Details

    • Difficulty:
      Unknown
    • Similar issues:

      Description

      List of issues :

        Issue Links

          Activity

          Hide
          Marius Dumitru Florea added a comment -

          I think we should enforce XHTML5 on our side by using an XHTML5 validator in our web-standards tests, but use the HTML5 (relaxed) doctype in the response. I don't expect the browsers to have problems rendering XHTML5 as HTML5, HTML5 is supposed to be very permissive after all, so I expect it to handle correctly an image tag closed with </img>. I haven't tested though.

          Show
          Marius Dumitru Florea added a comment - I think we should enforce XHTML5 on our side by using an XHTML5 validator in our web-standards tests, but use the HTML5 (relaxed) doctype in the response. I don't expect the browsers to have problems rendering XHTML5 as HTML5, HTML5 is supposed to be very permissive after all, so I expect it to handle correctly an image tag closed with </img> . I haven't tested though.
          Hide
          Guillaume Delhumeau added a comment - - edited

          I close this issue since:

          • an HTML5 has already been introduced (see commits and XWIKI-10249)
          • Flamingo has a HTML5 doctype and Flamingo is the new default skin.

          However, I need to create new issues for the remaining work.

          Show
          Guillaume Delhumeau added a comment - - edited I close this issue since: an HTML5 has already been introduced (see commits and XWIKI-10249 ) Flamingo has a HTML5 doctype and Flamingo is the new default skin. However, I need to create new issues for the remaining work.
          Hide
          Guillaume Delhumeau added a comment -
          Show
          Guillaume Delhumeau added a comment - Created: XWIKI-10840 XWIKI-10839
          Hide
          Vincent Massol added a comment - - edited

          I think we should enforce XHTML5 on our side by using an XHTML5 validator in our web-standards tests, but use the HTML5 (relaxed) doctype in the response. I don't expect the browsers to have problems rendering XHTML5 as HTML5, HTML5 is supposed to be very permissive after all, so I expect it to handle correctly an image tag closed with </img>. I haven't tested though.

          I agree

          Show
          Vincent Massol added a comment - - edited I think we should enforce XHTML5 on our side by using an XHTML5 validator in our web-standards tests, but use the HTML5 (relaxed) doctype in the response. I don't expect the browsers to have problems rendering XHTML5 as HTML5, HTML5 is supposed to be very permissive after all, so I expect it to handle correctly an image tag closed with </img>. I haven't tested though. I agree
          Hide
          Vincent Massol added a comment - - edited

          One different with XHTML1 I found indeed:

          Note that XHTML 1.0 previously defined that documents adhering to the compatibility guidelines were allowed to be served as text/html, but HTML 5 now defines that such documents are HTML, not XHTML.

          Also note that HTML5 is not a SGML syntax, it's just inspired by SGML and a SGML conformance checker cannot be used to validate HTML5 (see http://www.w3.org/TR/html5/single-page.html#conformance-requirements ).

          Also found this to confirm it at http://stackoverflow.com/a/11428285 :

          However you should note that HTML5 validation is different to that for previous versions of HTML. Previous versions of HTML depended on a DTD and followed an SGML validation model, HTML5 no longer has a DTD or any link to SGML. It's possible that what you want is not an HTML5 validator, but an HTML5 linter.

          Show
          Vincent Massol added a comment - - edited One different with XHTML1 I found indeed: Note that XHTML 1.0 previously defined that documents adhering to the compatibility guidelines were allowed to be served as text/html, but HTML 5 now defines that such documents are HTML, not XHTML. Also note that HTML5 is not a SGML syntax, it's just inspired by SGML and a SGML conformance checker cannot be used to validate HTML5 (see http://www.w3.org/TR/html5/single-page.html#conformance-requirements ). Also found this to confirm it at http://stackoverflow.com/a/11428285 : However you should note that HTML5 validation is different to that for previous versions of HTML. Previous versions of HTML depended on a DTD and followed an SGML validation model, HTML5 no longer has a DTD or any link to SGML. It's possible that what you want is not an HTML5 validator, but an HTML5 linter.

            People

            • Assignee:
              Guillaume Delhumeau
              Reporter:
              Jerome Velociter
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Date of First Response: