11935 2011-02-01 10:07:06 +0000 [device] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. 2011-08-04 05:06:25 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#adoptionAgency P3 normal --- 1 contributor ian annevk hsivonen ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 44930 0 contributor 2011-02-01 10:07:06 +0000 Specification: Section: http://www.whatwg.org/specs/web-apps/current-work/#adoptionAgency Comment: There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. Posted from: 194.237.142.17 44931 1 annevk 2011-02-01 10:12:00 +0000 It is not self-closing and therefore needs no mention. 44939 2 zcorpan 2011-02-01 12:26:40 +0000 I dunno, the content model is Empty and the example uses it as a void element, so maybe it was intended to make it a void element in the parser too. 44941 3 hsivonen 2011-02-01 13:34:01 +0000 Considering the Degrade Gracefully design principle, it seems like a bad idea to mint new void elements that get used in a general phrasing context. (In the case of <source> and <track>, there's at least the <video> container.) Can <device> be made non-void with the element content used for a "get yourself a newer browser" message? 45110 4 ian 2011-02-03 22:10:48 +0000 <device> hasn't really been thoroughly thought through yet... we need implementation experience to really know how it should work. I'm interested in hearing how people think the fallback should work. In particular, I'm interested in seeing realistic pages that would use <device> yet have fallback. In practice I think most of the time pages will only be using <device> after they have featured-tested for it, so I really don't think we need declarative fallback and I don't think it's a problem that it doesn't degrade to the same DOM in the parser. But I don't know, because I haven't seen realistic demo pages yet. 45112 5 contributor 2011-02-03 22:41:26 +0000 Checked in as WHATWG revision r5829. Check-in comment: add a note about <device> parsing http://html5.org/tools/web-apps-tracker?from=5828&to=5829 46265 6 ian 2011-03-04 01:02:02 +0000 We'll probably change to an API rather than an element so this might become a non-issue. 46708 7 ian 2011-03-15 06:03:44 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: <device> is gone. 53077 8 mike 2011-08-04 05:06:25 +0000 mass-moved component to LC1