Summary: | Add FeatureObserver for marquee and reflection | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Julien Chaffraix <jchaffraix> | ||||||
Component: | Layout and Rendering | Assignee: | Julien Chaffraix <jchaffraix> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | eae, eric, esprehn+autocc, leviw, ojan.autocc, ojan, simon.fraser, webkit.review.bot | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Attachments: |
|
Description
Julien Chaffraix
2013-02-28 15:02:46 PST
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. |