These 2 features are still proprietary / prefixed and we will need to unprefix them some day. In order to know if that's an option, we need to gather some numbers about their popularity. That's where FeatureObserver kicks in.
Created attachment 190823 [details] Proposed change.
Comment on attachment 190823 [details] Proposed change. Great! I'm really curious :)
What are you trying to observe? <marquee> or overflow: -webkit-marquee ?
(In reply to comment #3) > What are you trying to observe? <marquee> or overflow: -webkit-marquee ? Both, basically whenever we create a RenderMarquee on a page. For now, I am not really concerned by what generated the marquee. If needed, we can always add more granularity.
(In reply to comment #4) > (In reply to comment #3) > > What are you trying to observe? <marquee> or overflow: -webkit-marquee ? > > Both, basically whenever we create a RenderMarquee on a page. For now, I am not really concerned by what generated the marquee. If needed, we can always add more granularity. It's obvious that <marquee> is pretty popular (perhaps less so with the demise of Geocities).
Created attachment 190833 [details] Proposed change 2: Split marquee between <marquee> and overflow: -webkit-marquee.
Comment on attachment 190833 [details] Proposed change 2: Split marquee between <marquee> and overflow: -webkit-marquee. LGTM, but I'll wait for smfr.
Comment on attachment 190833 [details] Proposed change 2: Split marquee between <marquee> and overflow: -webkit-marquee. Clearing flags on attachment: 190833 Committed r144456: <http://trac.webkit.org/changeset/144456>
All reviewed patches have been landed. Closing bug.