This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html Section: http://www.whatwg.org/specs/web-apps/current-work/#poster-frame Comment: poster frame algo doesn't handle absent poster attribute Posted from: 91.181.37.224
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: If you're referring to the algorithm that starts "If the specified resource is to be used..." then it isn't relevant when the attribute is missing, since it only applies when there is a specified resource.
Some clarification would be welcome, then. Does "the specified resource" refer to the poster or the video? Also, the algorithm should be run "when the poster attribute is [...] removed", so it seems like it should handle being run without a poster attribute.
So it's correct when I complain, and wrong when you do? I'm confused... *** This bug has been marked as a duplicate of bug 12354 ***
mass-move component to LC1