14259 2011-09-23 13:30:49 +0000 <track> Drop Timestamp Objects on the floor instead of exposing as PIs 2012-07-18 18:39:00 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#webvtt-cue-text-dom-construction-rules P3 normal Unsorted 1 contributor ian ian mike philipj zcorpan contributor oldest_to_newest 57226 0 contributor 2011-09-23 13:30:49 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/the-iframe-element.html Multipage: http://www.whatwg.org/C#webvtt-cue-text-dom-construction-rules Complete: http://www.whatwg.org/c#webvtt-cue-text-dom-construction-rules Comment: Drop Timestamp Objects on the floor instead of exposing as PIs Posted from: 88.131.66.80 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.21 Safari/535.2 57228 1 zcorpan 2011-09-23 13:34:02 +0000 Exposing the timestamp as a PI is not very useful. If the author wants to use the timestamp info, he would need to parse them out manually and split the que into separate elements. We discussed wrapping the time blocks in separate elements (spans) instead of using PIs, but in the end concluded that we'd rather defer satisfying this narrow use case sometime in the future (if ever), and dropping the PI now. 57667 2 ian 2011-10-02 18:31:22 +0000 Isn't exposing them in a difficult way better than not exposing them at all? 58593 3 ian 2011-10-20 23:14:47 +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: Did Not Understand Request Change Description: no spec change Rationale: see comment 2