Project

General

Profile

Bug #10923

WidgetSet mode doesn't bootstrap properly

Added by Roel Standaert 19 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
09/08/2022
Due date:
% Done:

0%

Estimated time:

Description

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.


Related issues

Related to Bug #9076: Opening popup (calendar) of Wt::WDateEdit fails in Widgetset mode on first render.ResolvedKorneel Dumon09/17/2021

Actions
#1

Updated by Roel Standaert 19 days ago

  • Related to Bug #9076: Opening popup (calendar) of Wt::WDateEdit fails in Widgetset mode on first render. added

Also available in: Atom PDF