-
Notifications
You must be signed in to change notification settings - Fork 24
We should switch away from meta/@http-equiv #351
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workingrelease-blockerThe dev branch must not be merged into master while a release-blocker bug is open.The dev branch must not be merged into master while a release-blocker bug is open.validation and diagnosticsWork to be done on the schema, schematron, or the diagnosticsWork to be done on the schema, schematron, or the diagnostics
Milestone
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingrelease-blockerThe dev branch must not be merged into master while a release-blocker bug is open.The dev branch must not be merged into master while a release-blocker bug is open.validation and diagnosticsWork to be done on the schema, schematron, or the diagnosticsWork to be done on the schema, schematron, or the diagnostics
As with issue #350, the VNU validator nightly is now marking
<meta http-equiv="Content-Type".../>as invalid in XHTML5 documents; we should switch this off in our Saxon transformations that generate HTML and use an explicit<meta charset="UTF-8"/>instead.