When progressive bootstrap is enabled, setting a WContainerWidget's tag name to "form" causes it to be skipped in the DOM tree
By "skipped" I mean the element in question is not included in the DOM, but its children are, at its level. See the example below.
- Clone Wt into a subfolder wt of the attached archive (checkout tag 4.5.0)
mkdir build && cd build
cmake .. && make
./bugdemo --docroot . --http-listen 127.0.0.1:8080 -c ../wt_config.xml
- Point a browser at localhost:8080
- Inspect the text element
<div class="div1"> <form class="div2"> <div class="div3"> <span>Bug demo</span> </div> </form> </div>
<div class="div1"> <div class="div3"> <span>Bug demo</span> </div> </div>
If you do not use the attached
wt_config.xml (or otherwise disable progressive bootstrap) the DOM structure is as expected. If you change
div2's tag name to anything other than
foo) the DOM structure is as expected.
If I'm not mistaken, this would lead to a form-in-form in progressive bootstrap, which is invalid html.
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.
Updated by Captain Crutches 17 days ago
What outer form? I'm not nesting any forms, this is the only one on the page...
greps around frantically
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...?
Updated by Roel Standaert 16 days ago
That's more of a caveat that's specific to just Wt in general. You're just not supposed to use
<form> tags with Wt.