Closed
Bug 699912
Opened 13 years ago
Closed 13 years ago
HTML Parse Errors in https://build.mozilla.org/trychooser/
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dholbert, Unassigned)
References
Details
While glancing at https://build.mozilla.org/trychooser/ page-source in Nightly, I noticed a bunch of red tags from HTML parser errors. In particular: (1) All </input> close tags are all highlighted in red, since they're invalid. As noted at https://developer.mozilla.org/en/HTML/Element/Input : "Must have a start tag and must not have an end tag." (it's like <img>) (2) Unbalanced </strong> close-tag after "Android-Only Talos Suites:" (appears to be unnecessary, since the <h4> already bolds the text) (3) Unbalanced </ul> close-tag at the bottom of the "Talos Suites:" section (4) Also </form> and </body> are highlighted in red at the end of the document -- not sure why, possibly because there's an unclosed > <div> <!-- wrapper div--> at the end of the document just before the </form> tag.
Reporter | ||
Comment 1•13 years ago
|
||
(note that you need a recent Nightly in order to have these errors highlighted in the view-source UI -- see http://hsivonen.iki.fi/view-source/ for details.)
Reporter | ||
Comment 2•13 years ago
|
||
(also: this line
> <link rel="stylesheet" type="text/css" href="trychooser.css" />
probably wants to be in the <head> rather than in the <body>)
Comment 3•13 years ago
|
||
Thanks for catching these, I've made the cleanup changes landed and deployed - should be up in ~30 mins. http://hg.mozilla.org/build/tools/rev/98cdfccd36c0
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•