Closed Bug 619531 Opened 14 years ago Closed 14 years ago

Replace <article> tag on new submission pages with semantically applicable tag

Categories

(Input :: General, defect, P2)

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wenzel, Assigned: chowse)

Details

As davedash points out, the sections on the new submission pages are <article>s, which is semantically questionable. <article> is for "content from an external source". Unfortunately, we already have a <section> inside this article, so just changing it to section might not be the way to go. Chowse, can you suggest a change? (WONTFIXing this is also an option).
(In reply to comment #0) > As davedash points out, the sections on the new submission pages are > <article>s, which is semantically questionable. <article> is for "content from > an external source". I'm going to argue against this (and not sheerly out of laziness ;). According to the HTML5 spec: "The article element represents a self-contained composition in a document, page, application, or site and that is, in principle, independently distributable or reusable, e.g. in syndication. This could be a forum post, a magazine or newspaper article, a blog entry, a user-submitted comment, an interactive widget or gadget, or any other independent item of content." (http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-article-element) I believe the individual 'forms' of the feedback page fit this criteria of 'self-contained' content: they can exist and be understood even removed from the surrounding context. This is especially evident in the case of the Beta Feedback pages: each is accessed directly from the Feedback page, not by way of a 'landing' page. If you feel a change to <section> elements is still necessary, you can address this by changing any reference to "article" in the CSS to "body > section", or by adding a unique class to the articles-turned-sections and referencing them by the appropriate class selector.
Point taken.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.