Bug 34381 - Incomplete repaint of YouTube timeline thumb while scrolling
Summary: Incomplete repaint of YouTube timeline thumb while scrolling
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: GoogleBug, HasReduction, InRadar
Depends on:
Blocks:
 
Reported: 2010-01-30 18:12 PST by mitz
Modified: 2016-10-07 16:39 PDT (History)
1 user (show)

See Also:

Attachments
Reduction (506 bytes, text/html)
2010-01-30 18:12 PST, mitz 		no flags Details
Override -setNeedsDisplayInRect: and adjust the invalid rects during scrolling (3.16 KB, patch)
2010-02-22 23:06 PST, mitz 		simon.fraser: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mitz 2010-01-30 18:12:51 PST 
Created attachment 47778 [details]
Reduction

The timeline thumb on YouTube videos using a custom <video> controller leaves trails behind if the page is scrolled while the video is playing. This is apparently caused by a scroll event listener that forces layout, and can be reproduced with the attached reduction by scrolling it slowly, either by Option-dragging the scroller or scrolling with a Magic Mouse.
Comment 1 mitz 2010-01-30 18:13:54 PST 
This happens in TOT as well as in Safari 4.0.4.
Comment 2 mitz 2010-02-03 22:05:27 PST 
<rdar://problem/7611158>
Comment 3 mitz 2010-02-22 23:06:33 PST 
Created attachment 49267 [details]
Override -setNeedsDisplayInRect: and adjust the invalid rects during scrolling
Comment 4 Simon Fraser (smfr) 2010-02-23 07:53:54 PST 
Comment on attachment 49267 [details]
Override -setNeedsDisplayInRect: and adjust the invalid rects during scrolling

r=me

I guess it's not possible to do a repaint test?
Comment 5 mitz 2010-02-23 09:55:20 PST 
Fixed in <http://trac.webkit.org/projects/webkit/changeset/55159>.
Comment 6 Simon Fraser (smfr) 2016-10-07 16:39:29 PDT 
Followup fix in bug 163154.