Wt

WidgetSet skips the loading of Boot.js. It doesn't need to, since it can immediately start loading Wt's JavaScript.

However, this means that some things are skipped over, resulting in WEnvironment not being correctly populated.

With WidgetSet mode, the following functions won't return an accurate result:

• WEnvironment::webGL(): always false
• WEnvironment::screenWidth(): always -1
• WEnvironment::screenHeight(): always -1
• WEnvironment::timeZoneOffset(): always zero
• WEnvironment::timeZoneName(): always empty
• WEnvironment::supportsCookies(): no test cookie is set, so if there are no existing cookies already being sent by the browser this will be false

Another oddity when loading WidgetSet is that the initial script request does not actually load the contents of the widget. Instead, only Wt.js is loaded and the load signal is dispatched. Related to this is issue #9076: invisible changes were not being loaded as part of the load signal's response.