html validation errors in blueprint workload

Bug #139190 reported by Neal McBurnett
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Low
Unassigned

Bug Description

The blueprint workload page in launchpad has html validation errors.

I've attached the 6 errors in this small example page:

 https://blueprints.edge.launchpad.net/~ubuntu-instserv-dev/+specworkload

Even more useful would be plain text or rdf output for this data, to make it easier to extract and analyze blueprint relationships and status.

Revision history for this message
Neal McBurnett (nealmcb) wrote :
Neal McBurnett (nealmcb)
description: updated
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

These errors are not particular to the blueprint workload page: the same six errors occur on every Launchpad page (though some pages have other errors too).

The first error, "document type does not allow element 'noscript' here", is because we use <noscript> to provide CSS to make the boxes on the side of the page accessible if JavaScript is not available, and XHTML1 disallows <noscript> in <head>. Previously we expanded the boxes by default and then used JavaScript to collapse them after the page load, but while valid XHTML, this was unacceptably flickery. <noscript> in <head> is supported in all relevant browsers, degrades gracefully in all other browsers, and is currently specified as valid in HTML5. I don't intend to change this, unless someone comes up with an approach that is simple, valid, and non-flickery.

The second, third, and fourth errors are errors in the validator itself, assuming that we omitted an <object> tag when we didn't.

The fifth and sixth errors, "there is no attribute 'lpm:mid'", I don't understand. We are declaring the lpm namespace, so the validator should be ignoring attributes in that namespace.

Curtis Hovey (sinzui)
affects: launchpad-foundations → blueprint
Changed in blueprint:
importance: Undecided → Low
status: New → Triaged
Curtis Hovey (sinzui)
Changed in blueprint:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.