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/rendering.html Section: http://www.whatwg.org/specs/web-apps/current-work/#the-marquee-element-0 Comment: Describe the loop attribute on <marquee> Posted from: 83.218.67.122 User agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.8.131 Version/11.10
The spec does not mention <marquee loop>, but in my ad-hoc testing Opera and Firefox support it. It seems to originally be a proprietary IE invention, described in http://msdn.microsoft.com/en-us/library/ms534135(v=vs.85).aspx While of course it should be invalid, the spec should say that loop="foo" is equivalent to marquee-loop: foo in CSS, see http://www.w3.org/TR/css3-box/#marquee-loop (This would mean that loop is a boolean attribute on <audio> and <video> but a numeric attribute on <marquee>, which is why I noticed the absence of <marquee loop> to begin with.)
Hmm, I shouldn't file bugs on Fridays... It's already defined, just in another section: http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html#marquee-loop-count I'll leave the bug open for the editor to decide whether or not to link between or otherwise consolidate these sections, and possibly listing <marquee loop> in the attribute summary section.
Also, perhaps all of the loop state algorithm could be replaced by a reference to http://www.w3.org/TR/css3-box/#marquee-loop
(In reply to comment #2) > Hmm, I shouldn't file bugs on Fridays... It's already defined, just in another > section: > http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html#marquee-loop-count > > I'll leave the bug open for the editor to decide whether or not to link between > or otherwise consolidate these sections, and possibly listing <marquee loop> in > the attribute summary section. There is already a link. The rendering section uses the "increment the marquee current loop index" algorithm which uses the attribute. (In reply to comment #3) > Also, perhaps all of the loop state algorithm could be replaced by a reference > to http://www.w3.org/TR/css3-box/#marquee-loop That spec doesn't seem to define a processing model. 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: nothing to change
mass-moved component to LC1