Closed Bug 521090 Opened 16 years ago Closed 16 years ago

[website] Jetpack homepage doesn't validate to its HTML 5 doctype

Categories

(Websites Graveyard :: jetpackgallery.mozillalabs.com, defect, P4)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: stephend, Unassigned)

References

()

Details

I don't know if this is valid, but we don't validate to our HTML 5 doctype: http://html5.validator.nu/?doc=http%3A%2F%2Fjetpack.stage.mozilla.com
Summary: Jetpack homepage doesn't validate to its HTML 5 doctype → [website] Jetpack homepage doesn't validate to its HTML 5 doctype
Made a couple updates. Validating now. == Sending views/template.php Transmitting file data . Committed revision r53350.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Ryan, I still see errors using the URL from comment 0; should I be using a different validator?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Oh, sorry Stephen. I ended up using the W3C Validator by habit instead of the one from validator.nu. We can keep this ticket open until those issues are resolved as well.
Severity: normal → minor
Priority: -- → P4
Whiteboard: [jetpack gallery]
Assignee: ryan → nobody
Component: Jetpack → jetpackgallery.mozillalabs.com
Product: Mozilla Labs → Websites
QA Contact: jetpack → jetpackgallery-mozillalabs-com
Target Milestone: -- → ---
Homepage now validates to the HTML5 doctype. Verified at: * http://html5.validator.nu/ * http://validator.w3.org/ == Sending application/views/jetpacks/jetpacks_view.php Sending application/views/jetpacks/jetpacks_view_reviews.php Sending application/views/template.php Sending public_html/css/main.css Transmitting file data .... Committed revision r57560.
Status: REOPENED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → FIXED
Verified FIXED: The document is valid HTML5 + ARIA (subject to the utter previewness of this service).
Status: RESOLVED → VERIFIED
Whiteboard: [jetpack gallery]
Target Milestone: --- → 1.2
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.