RESOLVED INVALID 23842
overflow-x: -webkit-marquee always scrolls text even if not too long 
https://bugs.webkit.org/show_bug.cgi?id=23842
Summary overflow-x: -webkit-marquee always scrolls text even if not too long
aurelien.baudet
Reported 2009-02-09 01:31:10 PST
According to CSS3, the marquee effect on overflow-x is only started if the content is too long (http://www.w3.org/TR/css3-box/#marquee). On Webkit r40771, the marquee effect is always started
Attachments
Simple test to demonstrate marquee bug (477 bytes, text/html)
2012-09-24 05:33 PDT, steve_sims7 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
steve_sims7
Comment 1 2012-09-24 05:33:44 PDT
Created attachment 165358 [details] Simple test to demonstrate marquee bug The attached file is a simple demonstration of this bug. I can confirm that, as per the original but description, overflow-x: -webkit-marquee is always scrolling text even if it's not overflowing. I'm seeing this bug in Safari 6, Chrome 21, iTunes 10.7 (in iTunes LPs), WebKit Nightly (as per 23rd September 2012), all on Mac OS X 10.8, as well as Safari and UIWebView on iOS 6. This bug is *not* present in Safari 5 on Mac OS X, or Safari/UIWebView on iOS 5.0 or 5.1.
Victor
Comment 2 2012-10-30 14:24:38 PDT
I can confirm that this issue is still present on the lasted webkit buid as of Octuber 30, 2012 (WebKit r132908). This is another page/example, demonstrating the issue: http://victmo.com/marquee-bug.html I also checked on lastest Chrome canary build and the problem is still present (bug 158472: http://code.google.com/p/chromium/issues/detail?id=158472).
Ahmad Saleem
Comment 3 2022-07-13 11:29:32 PDT
marquee properties are not supported by browsers and following commit removed various -webkit-marquee properties support (which are also used in this bug): https://github.com/WebKit/WebKit/commit/57353ad402d37b33974920d7f925d9fa96a288ef Since it was non-standard support and now marquee behavior is achieved via CSS Animations and Transforms etc., can this be closed? Thanks!
Note You need to log in before you can comment on or make changes to this bug.