Closed
Bug 884772
Opened 12 years ago
Closed 11 years ago
Article histories don't validate
Categories
(support.mozilla.org :: Knowledge Base Software, task, P4)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
RESOLVED
FIXED
2013Q4
People
(Reporter: scoobidiver, Assigned: kudrom)
Details
(Whiteboard: u=dev c=general p=0 s=2013.25 [mentor=r1cky])
There are 12 errors for the chosen example!
See http://validator.w3.org/check?uri=https%3A%2F%2Fsupport.mozilla.org%2Fen-US%2Fkb%2Fhow-to-enable-java-if-its-been-blocked%2Fhistory&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.3+http%3A%2F%2Fvalidator.w3.org%2Fservices
Updated•12 years ago
|
Whiteboard: u=dev c=general p= s=2013.backlog [mentor=r1cky]
| Assignee | ||
Comment 1•11 years ago
|
||
Hi,
The async error is due to the difference in syntax between the html5 spec [1] and the real implementation of some browsers that need the attribute to be true or false, so i don't know what to do, wheter to make it html5 compilant or to leave it like it is and protect legacy browsers. I suppose that the latter is the most important thing.
I have made a pull request with the noindex attribute deleted (it can only be in the robots meta tag): https://github.com/mozilla/kitsune/pull/1778
bye
[1] http://www.w3.org/html/wg/drafts/html/master/scripting-1.html#async
Comment 2•11 years ago
|
||
Landed on master:
https://github.com/mozilla/kitsune/commit/cbd70843a696aca92ca6925c2937f8da22f94e8e
This won't get deployed to production until the new year because we have frozen our prod systems until then.
Thanks!!!
Assignee: nobody → kudrom
Priority: -- → P4
Whiteboard: u=dev c=general p= s=2013.backlog [mentor=r1cky] → u=dev c=general p= s=2013.25 [mentor=r1cky]
Target Milestone: --- → 2013Q4
Comment 3•11 years ago
|
||
Deployed to prod now!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Whiteboard: u=dev c=general p= s=2013.25 [mentor=r1cky] → u=dev c=general p=0 s=2013.25 [mentor=r1cky]
You need to log in
before you can comment on or make changes to this bug.
Description
•