#11300: Switch to HTML5
---------------------------+------------------------------------------------
 Reporter:  spliter        |       Owner:  spliter 
     Type:  PLIP           |      Status:  assigned
 Priority:  major          |   Milestone:  4.2     
Component:  Templates/CSS  |    Keywords:          
---------------------------+------------------------------------------------

Comment(by spliter):

 Replying to [comment:71 alecm]:
 > Regarding the mdash validation error.  I'm using the validator here:
 http://validator.w3.org/#validate_by_input which is of course experimental
 for HTML5, but I suspect other people will use it.  I view the source for
 the front-page in my browser and copying and pasting it into the text box.
 The validator automatically detects that the page is HTML5 and utf8.  It
 has an issue with the mdash that Plone puts in the title tag, as well as
 with the http-equiv="Content-Type" meta tag.  I don't think these are
 terribly important since the validator.nu validator appears to be the
 better one.

 Thanks for the explanation, Alec. Then, I suppose this is very minor
 issue. I validate from Firefox, using WebDeveloper Tools' "Validate local
 HTML" feature. It sends the local site's (in our case running on
 localhost:8080/Plone) output to the official w3c validator as well. In
 this case there are no validation errors and the document is validated as
 fully valid HTML5 document. Dunno, maybe the ways they process the direct
 input is different, but since validator.nu doesn't raise an error as well,
 I tend to think the 'direct input' feature of the official validator has
 issues.

 So, I suppose, we can conclude that the ticket is really ready for merge
 :)

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/11300#comment:72>
Plone <http://plone.org>
Plone Enterprise Content Management System
_______________________________________________
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
https://lists.plone.org/mailman/listinfo/plone-plip-advisories

Reply via email to