WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
65056
Enable fast path scrolling for composited iframes
https://bugs.webkit.org/show_bug.cgi?id=65056
Summary
Enable fast path scrolling for composited iframes
Adrienne Walker
Reported
2011-07-22 16:17:26 PDT
Enable fast path scrolling for composited iframes
Attachments
Patch
(6.88 KB, patch)
2011-07-22 16:24 PDT
,
Adrienne Walker
no flags
Details
Formatted Diff
Diff
Patch
(17.83 KB, patch)
2011-08-01 16:55 PDT
,
Adrienne Walker
no flags
Details
Formatted Diff
Diff
Patch
(17.65 KB, patch)
2011-08-02 09:52 PDT
,
Adrienne Walker
jamesr
: review+
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Adrienne Walker
Comment 1
2011-07-22 16:24:52 PDT
Created
attachment 101789
[details]
Patch
James Robinson
Comment 2
2011-07-22 16:36:03 PDT
Comment on
attachment 101789
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=101789&action=review
I'd like to see a test for the following testcase to see if it's OK to disregard the overlap test: <iframe id="a" class="composited"></iframe> <iframe id="b" class="noncomposited"></iframe> where b overlaps a i'm not 100% sure if b will be put into a composited layer in this case. If it always will, then I agree it's fine to ignore the overlap test when considering whether to fast scroll inside a's FrameView.
> Source/WebCore/page/FrameView.cpp:1150 > + if (contentsInCompositedLayer())
is it OK to ignore m_useSlowRepaints for composited layers?
Collabora GTK+ EWS bot
Comment 3
2011-07-22 17:35:51 PDT
Comment on
attachment 101789
[details]
Patch
Attachment 101789
[details]
did not pass gtk-ews (gtk): Output:
http://queues.webkit.org/results/9226327
Adrienne Walker
Comment 4
2011-07-22 18:04:45 PDT
(In reply to
comment #2
)
> (From update of
attachment 101789
[details]
) > View in context:
https://bugs.webkit.org/attachment.cgi?id=101789&action=review
>
> > Source/WebCore/page/FrameView.cpp:1150 > > + if (contentsInCompositedLayer()) > > is it OK to ignore m_useSlowRepaints for composited layers?
setUseSlowRepaints() is called in three places, all in RenderView. All of which appear to be related to layers that have reflections, transforms, or transparency. If you were doing this in software, I could see how these might cause blitting problems when scrolling. However, if the layer has its own backing, none of these should be an issue. I was tempted to rename this to setCannotBlitToWindow() to make this more clear. I can also add more tests for all these cases. :)
Adrienne Walker
Comment 5
2011-08-01 16:55:47 PDT
Created
attachment 102591
[details]
Patch
Gustavo Noronha (kov)
Comment 6
2011-08-02 07:37:30 PDT
Comment on
attachment 102591
[details]
Patch
Attachment 102591
[details]
did not pass gtk-ews (gtk): Output:
http://queues.webkit.org/results/9284720
Adrienne Walker
Comment 7
2011-08-02 09:06:33 PDT
Comment on
attachment 102591
[details]
Patch Taking off review until I can address that gtk issue.
Adrienne Walker
Comment 8
2011-08-02 09:52:14 PDT
Created
attachment 102661
[details]
Patch
Adrienne Walker
Comment 9
2011-08-02 09:53:26 PDT
(In reply to
comment #8
)
> Created an attachment (id=102661) [details] > Patch
Whoops, forgot the #if guard for accelerated compositing. Thanks, ews bot!
Adrienne Walker
Comment 10
2011-08-03 16:37:55 PDT
***
Bug 61806
has been marked as a duplicate of this bug. ***
James Robinson
Comment 11
2011-08-10 12:29:26 PDT
Comment on
attachment 102661
[details]
Patch R=me
Adrienne Walker
Comment 12
2011-08-11 13:43:29 PDT
Committed
r92874
: <
http://trac.webkit.org/changeset/92874
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug