From cfbbbd65b8f091bbbc13387b347140136e137881 Mon Sep 17 00:00:00 2001 From: smcv Date: Sun, 5 Oct 2014 09:06:20 -0400 Subject: new --- doc/todo/generate_HTML5_by_default.mdwn | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 doc/todo/generate_HTML5_by_default.mdwn diff --git a/doc/todo/generate_HTML5_by_default.mdwn b/doc/todo/generate_HTML5_by_default.mdwn new file mode 100644 index 000000000..3adce8c90 --- /dev/null +++ b/doc/todo/generate_HTML5_by_default.mdwn @@ -0,0 +1,33 @@ +The `html5` option was added in 2010 and marked as "not experimental" in 2011 +but is not the default. + +According to , current versions of +all recent versions of all major browsers - even IE - support the HTML5 +semantic elements (`
` etc.), except for `
` which IkiWiki +doesn't use anyway. With that being the case, I'm not sure whether we gain +anything from not generating HTML5 (or "HTML" as it's now labelled) all the time. + +In particular, non-HTML5 mode uses `` +which doesn't allow newer markup like the `role` attribute, so we can't close +[[todo/add_aria_landmarks_to_make_ikiwiki_websites_more_accessible]] while +remaining XHTML 1.0 Strict. The recommended pseudo-doctype for HTML5, and for +HTML with ARIA markup, is ``. + +(I do think we should continue to use `` and output +well-formed XML so people who want to do XSLT tricks with IkiWiki's output +can do so, though.) + +In practice, real browsers have never actually implemented a strict XHTML mode: +they've always parsed `text/html` as "tag soup", because they need a tag-soup +parser anyway, and nobody wants to maintain two parsers. + +Options include: + +* set html5 to 1 by default but retain the dual-mode templates +* remove the option and always behave as if it had been 1, simplifying + the templates + +Thoughts? + +--[[smcv]] -- cgit v1.2.3