Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

prioritize_critical_css breaks XHTML 1.0 Strict validation #691

Open
GoogleCodeExporter opened this issue Apr 6, 2015 · 3 comments
Open

Comments

@GoogleCodeExporter
Copy link

The new filter prioritize_critical_css inserts the CSS as 
<style>...</style>

This breaks XHTML 1.0 Strict validation, as it should be 
<style type="text/css">...</style>



Original issue reported on code.google.com by rwap.services on 9 May 2013 at 3:42

@GoogleCodeExporter
Copy link
Author

Are you seeing browser breakages or just validation failures?  I'm thinking we 
should probably fix this up in the "pedantic" filter if it just breaks 
validation, as that's specifically what that filter is for.

Original comment by jmaes...@google.com on 10 May 2013 at 2:19

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

This is just a validation error so far as I know - I don't whether there might 
be any browsers which would have a problem with the fact it is just 
<style>...</style>

Original comment by rwap.services on 10 May 2013 at 2:29

@GoogleCodeExporter
Copy link
Author

It does seem to be just a validation error.

Another validation error is caused by the insertion of the dns-prefetch, for 
example:

<link rel="dns-prefetch" href="//www.lduhtrp.net">

instead of:
<link rel="dns-prefetch" href="//www.lduhtrp.net" />

Original comment by rwap.services on 22 May 2013 at 10:10

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant