> I was wondering if it causes any HTML validation problems for other
doctypes?
True. A strict validator for XHTML will flag HTML5 syntax as an error. It
isn't a part of the XHTML spec. From my testing it seems like modern
browsers can handle this, but you're right, validators will catch it.
> If
I was wondering if it causes any HTML validation problems for other
doctypes? If so, we might document that Django's default HTML rendering
targets the HTML5 doctype.
On Saturday, July 23, 2016 at 4:21:22 AM UTC-4, Florian Apolloner wrote:
>
> This should be perfectly fine -- I guess just nobody
This should be perfectly fine -- I guess just nobody got around to do it
yet. The main issue with the HTML5 stuff is around date&time where it is
not clearly specified (or was last time I looked) what the UA should send
and how to handle that in browsers not supporting HTML5 yet (ie sending iso
Le vendredi 22 juillet 2016 23:30:58 UTC+2, Jon Dufresne a écrit :
>
> Hi,
>
> I would like to propose that Django renders the "checked" attribute of
> checkbox and radio inputs using the HTML5 boolean style attributes.
>
(...)
I'm definitely +1 with this change.
Hopefully, 1.11 should come with
Hi,
I would like to propose that Django renders the "checked" attribute of
checkbox and radio inputs using the HTML5 boolean style attributes.
Django has supported HTML5 boolean attributes since 1.8 [0]. It has used
them internally for the "disabled" attribute since 1.9 [1] and the
"required" att
