What's New

In May 2020, Tobago 4.5 was released with some bugfixes and new features.

• Sheet: Lazy loading rows by scroll events
• Using Bootstrap für toggle, checkbox and radio buttons
• Outline markup for buttons
• Update to Bootstrap 4.4.1
• Update to jQuery 3.5.0
• Bugfixes

In March 2019, Tobago 4.4 was released with some bugfixes and new features.

• A context message can now be added to form-component.
• Update to Bootstrap 4.3.1
• <tc:date> todayButton
• Placeholder attribute for <tc:file>
• Markups for text
• Bugfixes

In September 2018, Tobago 4.3 was released with some bugfixes and new features.

• New toggle component: <tc:selectBooleanToggle>
• Update to Bootstrap 4.1.3
• Update to jQuery 3
• Vertical align vor Sheets
• "plain" attribute
• "keepLineBreaks" attribute
• Icons in FacesMessages
• tooltop for <tc:badge>
• java.util.Calendar and java.time.DateTime support for <tc:date>
• LabelLayout attributes gridLeft, gridRight
• Passwords aren't sent to the client
• Bugfixes

In April 2018, Tobago 4.2 was released with some bugfixes and new features.

• Desktop-like vertical layout is possible (like in Tobago 2), use markup="spread"
• New component <tc:badge/> badge
• <tc:selectReference> is fixed
• Better compatibility with Mojarra
• Theme Charlotteville
• Many other enhancements and bugfixes

In February 2018, Tobago 4.1 was released with some bugfixes and new features.

• Update to Bootstrap 4.0.0 (final)
• New component for rating: <tc:stars>
• Converter for tab label and box label
• Change style of <tc:tabGroup> to Bootstrap 4

After the last major release in December 2016, Tobago 4 comes with 127 changes, bugfixes and new features in December 2017.

In general, the step to version 4 is quite compatible, so the migration is easy. Please follow the Migration from Tobago 3 to 4 guide.

In September 2018, Tobago 3.1 was released with some bugfixes and new features.

• Update to jQuery 3
• Passwords aren't sent to the client
• Bugfixes

Until Tobago 2.0 the layout was computed on the server, to make advanced features available for comfortable web application.

With CSS3 and HTML5 it is possible these days, to make advanced layout managers implemented in the browser.

The base theme that comes with Tobago changes from plain CSS to Twitters Bootstrap. So your applications have the advantage of modern HTML5 web applications with less coding.

• Segment Layout (uses the 12 columns layout from Bootstrap)
• Flex Layout (CSS3)
  You may replace the GridLayout from Tobago 2.0 with FlexLayout.
• Flow Layout
• The new layout managers have been written a bit more concised: Using as container instead of a facet.

• The tx library is no longer needed
• The label is integrated into the tc library.
• This results in a more intuitive API
• Rich variations of positioning the label with new attribute labelLayout

• <tc:section>
• <tc:header> & <tc:footer>
• <tc:figure>

• The <tc:in/> tag may be extended to an Input Group.
• A size attribute is added for
  • <tc:selectOneListbox>,
  • <tc:selectManyListbox>,
  • <tc:selectManyShuffle> and
  • <tc:treeListbox>.
• Only disabled="true" must be set to disable an image.
• <tc:sheet>
  • Constraints are no longer needed to set a multi-line header.
  • A width can be defined for columns which will influence the auto layout of the browser.

• Using standard ajax mechanism.
• The clientId will be now rendered to the root element in HTML of a component.
• Change the icon format from GIF to PNG.

There is a new collapsible concept for <tc:box>, <tc:section>, <tc:panel> and <tc:popup> where the collapse state can be switched via an <tc:operation>.

• File upload now uses Servlet 3.0 instead of Commons Fileupload. This simplifies the setup.
• Font Awesome as an icon library.
• ARIA support codes are added. Those can be used in renderer classes.
• Resources can be excluded from parent theme.
• ResourceBundles support parameters
• The lang attribute of the HTML root tag will be rendered now.
• Messages are closeable now.
• Custom CSS classes can be added to a component.
• Support more units than 'px'. Now ex, em, mm, cm, in can be used as well.
• The link attribute of Button and Link does support rightClick -> newTab.

• The AutoAccessKey feature (using underscore to indicate next character as an access key) is removed. Now the accessKey attribute must be used.
• JSP support removed.
• The tag <tc:time> is removed. Use <tc:date> instead.

In January 2019, Tobago 2.4 was released with a new features.

• File upload switched from commons-fileupload to Servlet 3.0 specification.
  • You no long need to define a TobagoMultipartFormdataFilter in the web.xml
  • There is no longer a tobago-fileupload.jar
  • Remove the dependency to commons-fileupload.jar in your web app, if there is any.
  • If using JSF 2.0 or 2.1 you will need to add a tag <multipart-config> tag to the FacesServlet config in the <web.xml>.

In September 2018, Tobago 2.2 was released with some bugfixes and new features.

• Update to jQuery 3
• IE 8 is no longer supported
• PageState is usable for layout
• Passwords aren't sent to the client
• Bugfixes

• Using jQuery UI Datepicker and TimePicker Addon
• Faster — no server request
• Better interactivity
• Old Date-/TimePicker via tobago-config.xml

Draggable Popups

• New implementation
• Sub-Tag <tc:suggest>
• More configuration options

• Icons
• Toolbar buttons

• Looks pretty now in every browser

• Icons

• Integration example in the demo of CKEditor™ and TinyMCE
• Not included, because of incompatible licences or breaks CSP
• Other possible, but many have disadvantages

• Dependent from the focused input, the default command will be selected
• Markup to show the command to the user

• Big internal refactoring
• Work internally now with the JSF UIData
• Free model: DefaultMutableTreeNode is not required any longer, but you can implement javax.faces.model.DataModel
• TreeTable
• Infinite Trees possible
• Selectors: sub-tree selection

• Dynamic lists in <f:selectItems> need not glue code (JSF 2.0)
• Redirect in navigation rules doesn't break layout size
• Additional possibility to show paging arrows in sheet
• Automatically create accesskey from underscore is know configurable

• To prevent XSS
• W3C Standard
• Idea:
  • Don't execute any code inside the HTML file
    • No content in script tags
    • no onclick, nor on* etc.
  • Don't execute eval(script)
  • Don't apply CSS inside the HTML file
  • Define the sources of any resources
  • Strict separation of code and data
    • Keep the code in JavaScript Files
    • Put additional data in HTML5 data-* attributes
• Browser support: all current, but IE 10 and 11 only "sandbox"
• Activated by default, can be configured via tobago-config.xml
• There is also a "report-only" mode for development

• All renderers and scripts are refactored to be compliant with CSP
• Using application specific JavaScript in Tobago
  • script attribute in command tags is deprecated
  • Problem: when setting non of these attributes: action, script, link, Tobago will create a default action. This can't be changed without breaking compatibility.
  • Solution: omit="true"

• <tc:textarea>, when it contains a <tc:dataAttribute> with name="html-editor"
• <tc:out>, when escape="false"
• Default implementation: JSoup whitelist scanning
• Configurable via tobago-config.xml
• Why? See OSWAP

• Setting nosniff HTTP header (to prevent XSS)
• Don't allow to be in a frame (to prevent Frame-Attacks)
• Both are configurable via tobago-config.xml, default is secure

• Tree uses subclass of javax.faces.model.DataModel
• Using Java APT generator
• Using ' instead of " for HTML attributes (JSON friendly)
• JavaScript logging via console (plus workaround for old browsers)
• The theme-config.xml was merged with tobago-config.xml
• Access the Tobago configuration via the TobagoContext
• The TobagoConfig is immutable after initialization
• Add the version of Tobago into the resource URLs to avoid caching problem after updates