-
Notifications
You must be signed in to change notification settings - Fork 2k
Drop XHTML support and add html5 #845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sounds good to me! :) |
In In the same file, we could also remove old DOCTYPES snippets (XHTML, HTML4...) and only leave the one for HTML 5 DOCTYPE. What do you think? I would like to hear opinions before making a pull request trying to impose my changes. If you like this idea, I can make a pull request. I don't if @honza, as HTML Django maintainer, also maintains this or if he should review this first. |
I don't there is value in renaming snippets without good reason, it will confuse people who are used to typing Much more interested in the smaller more frequently typed ones. |
Below is the
|
Seems like it would be a good addition :) |
This breaks compatibility with XHTML (see honza#845). The slashes are even forbidden in HTML4 (but optional in HTML5). Source: <http://xahlee.info/js/html5_non-closing_tag.html>
This breaks compatibility with XHTML (see #845). The slashes are even forbidden in HTML4 (but optional in HTML5). Source: <http://xahlee.info/js/html5_non-closing_tag.html>
This breaks compatibility with XHTML (see honza#845). The slashes are even forbidden in HTML4 (but optional in HTML5). Source: <http://xahlee.info/js/html5_non-closing_tag.html>
I think it's not worth to support XHTML anymore. Instead there should be proper html5 templates.
See
UltiSnips/html.snippets
related: #804
The text was updated successfully, but these errors were encountered: