form.hidden_tag() generates unnecessary div

[txtsd]

If the input types are already hidden, what is the purpose of the div?

<input id="csrf_token" name="csrf_token" type="hidden" value="1452782070##2b535ebc0d609f21b85bb776d59247560414b7ff">
<input id="next" name="next" type="hidden" value="">

is a cleaner output than

<div style="display:none;"><input id="csrf_token" name="csrf_token" type="hidden" value="1452782070##2b535ebc0d609f21b85bb776d59247560414b7ff"><input id="next" name="next" type="hidden" value=""></div>

and avoids inlined css.

[pjvandehaar]

@txtsd Search for DIV tag on https://flask-wtf.readthedocs.org/en/latest/quickstart.html?highlight=div%20tag

[davidism]

@lepture Omitting the div appears to be valid HTML 5, but not 4. No decent HTML parser would be confused by the briefer syntax. Maybe it's time to re-evaluate removing this?

If the user wants to produce valid HTML 4, the validator is pretty clear about how to fix the issue. They can wrap it manually.

[lepture]

@davidism aye

[davidism]

Noticed that the docs contradicted themselves by rendering another field without a wrapping block right after the hidden block. So we weren't even following our own rules. ;-)