http://redmine.emweb.be/http://redmine.emweb.be/favicon.ico?16934085252021-01-05T20:20:08ZRedmineWt - Bug #7958: When progressive bootstrap is enabled, setting a WContainerWidget's tag name to "form" causes it to be skipped in the DOM treehttp://redmine.emweb.be/issues/7958?journal_id=274842021-01-05T20:20:08ZWim Dumonwim@emweb.be
<ul></ul><p>Hi,</p>
<p>If I'm not mistaken, this would lead to a form-in-form in progressive bootstrap, which is invalid html.</p>
<p>You cannot create form tags when using progressive bootstrap. The outer form is used to capture events in progressive bootstrap mode in case that no JS would be available.</p>
<p>BR,<br>
Wim.</p>
Wt - Bug #7958: When progressive bootstrap is enabled, setting a WContainerWidget's tag name to "form" causes it to be skipped in the DOM treehttp://redmine.emweb.be/issues/7958?journal_id=274852021-01-05T23:02:50ZCaptain Crutchescaptaincrutches@gmail.com
<ul></ul><p>What outer form? I'm not nesting any forms, this is the only one on the page...</p>
<p><em>greps around frantically</em></p>
<p>Oh... I see that the initial page that gets served, before we realize we have JS available, contains the entire widget content inside a form. I see what you mean now. That does seem like a rather important caveat to progressive bootstrap, and I don't see it documented anywhere. Did I miss something...?</p>
Wt - Bug #7958: When progressive bootstrap is enabled, setting a WContainerWidget's tag name to "form" causes it to be skipped in the DOM treehttp://redmine.emweb.be/issues/7958?journal_id=275012021-01-06T13:19:28ZRoel Standaertroel@emweb.be
<ul></ul><p>That's more of a caveat that's specific to just Wt in general. You're just not supposed to use <code><form></code> tags with Wt.</p>
<p>Wt simply has form widgets, and whenever a signal is sent, their value is updated. It's normally achieved through JavaScript, but when no JS support is available, that is achieved through a global <code><form></code> tag.</p>