WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
131425
Make page overlay functionality working on coordinated graphics.
https://bugs.webkit.org/show_bug.cgi?id=131425
Summary
Make page overlay functionality working on coordinated graphics.
Hyowon Kim
Reported
2014-04-08 20:56:00 PDT
Page overlay functionality is not working on coordinated graphics since
r166975
.
Attachments
Patch
(17.22 KB, patch)
2014-04-13 06:05 PDT
,
Hyowon Kim
no flags
Details
Formatted Diff
Diff
Patch
(19.93 KB, patch)
2014-04-13 09:05 PDT
,
Hyowon Kim
no flags
Details
Formatted Diff
Diff
patch for landing
(20.15 KB, patch)
2014-04-14 01:00 PDT
,
Hyowon Kim
no flags
Details
Formatted Diff
Diff
patch for landing
(16.92 KB, patch)
2014-04-14 19:15 PDT
,
Hyowon Kim
no flags
Details
Formatted Diff
Diff
Show Obsolete
(3)
View All
Add attachment
proposed patch, testcase, etc.
Hyowon Kim
Comment 1
2014-04-13 06:05:17 PDT
Created
attachment 229229
[details]
Patch
Hyowon Kim
Comment 2
2014-04-13 09:05:20 PDT
Created
attachment 229235
[details]
Patch
Darin Adler
Comment 3
2014-04-13 23:28:43 PDT
Comment on
attachment 229235
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=229235&action=review
> Source/WebCore/platform/graphics/texmap/coordinated/CompositingCoordinator.cpp:75 > +void CompositingCoordinator::setRootCompositingLayer(GraphicsLayer* CompositingLayer, GraphicsLayer* overlayLayer)
CompositingLayer should not be capitalized, since it’s an argument name.
> Source/WebCore/platform/graphics/texmap/coordinated/CompositingCoordinator.h:67 > + void setRootCompositingLayer(GraphicsLayer*, GraphicsLayer*);
Not clear what these two arguments are, so one or both need names here in the header.
> Source/WebKit2/WebProcess/WebPage/LayerTreeHost.h:79 > - virtual void didInstallPageOverlay(PageOverlay*) = 0; > - virtual void didUninstallPageOverlay(PageOverlay*) = 0; > - virtual void setPageOverlayNeedsDisplay(PageOverlay*, const WebCore::IntRect&) = 0; > + virtual void didInstallPageOverlay(PageOverlay*) { } > + virtual void didUninstallPageOverlay(PageOverlay*) { } > + virtual void setPageOverlayNeedsDisplay(PageOverlay*, const WebCore::IntRect&) { }
Not sure this is a good change. Is this really better than putting the empty functions in the derived class?
> Source/WebKit2/WebProcess/WebPage/PageOverlayController.cpp:224 > -void PageOverlayController::flushPageOverlayLayers(FloatRect visibleRect) > +void PageOverlayController::flushPageOverlayLayers(const FloatRect& visibleRect)
Not sure this is a good change. I know that we save a copy here, but Anders has been discouraging us from using const& everywhere.
Hyowon Kim
Comment 4
2014-04-14 01:00:02 PDT
Created
attachment 229270
[details]
patch for landing
Hyowon Kim
Comment 5
2014-04-14 01:02:09 PDT
(In reply to
comment #3
)
> (From update of
attachment 229235
[details]
) > View in context:
https://bugs.webkit.org/attachment.cgi?id=229235&action=review
> > > Source/WebCore/platform/graphics/texmap/coordinated/CompositingCoordinator.cpp:75 > > +void CompositingCoordinator::setRootCompositingLayer(GraphicsLayer* CompositingLayer, GraphicsLayer* overlayLayer) > > CompositingLayer should not be capitalized, since it’s an argument name.
Oops. Done. Source/WebCore/platform/graphics/texmap/coordinated/CompositingCoordinator.h:67
> > + void setRootCompositingLayer(GraphicsLayer*, GraphicsLayer*); > > Not clear what these two arguments are, so one or both need names here in the header.
Done.
> > Source/WebKit2/WebProcess/WebPage/LayerTreeHost.h:79 > > - virtual void didInstallPageOverlay(PageOverlay*) = 0; > > - virtual void didUninstallPageOverlay(PageOverlay*) = 0; > > - virtual void setPageOverlayNeedsDisplay(PageOverlay*, const WebCore::IntRect&) = 0; > > + virtual void didInstallPageOverlay(PageOverlay*) { } > > + virtual void didUninstallPageOverlay(PageOverlay*) { } > > + virtual void setPageOverlayNeedsDisplay(PageOverlay*, const WebCore::IntRect&) { } > > Not sure this is a good change. Is this really better than putting the empty functions in the derived class?
It's a temporary solution. These functions are not called anymore. But LayerTreeHostGTK still derives them from LayerTreeHost. They would be removed if GTK port fixes this issue too.
> > Source/WebKit2/WebProcess/WebPage/PageOverlayController.cpp:224 > > -void PageOverlayController::flushPageOverlayLayers(FloatRect visibleRect) > > +void PageOverlayController::flushPageOverlayLayers(const FloatRect& visibleRect) > > Not sure this is a good change. I know that we save a copy here, but Anders has been discouraging us from using const& everywhere.
Okay. Undo adding const&. Thank you for the review!
Jae Hyun Park
Comment 6
2014-04-14 18:04:04 PDT
(In reply to
comment #4
)
> Created an attachment (id=229270) [details] > patch for landing
This may not be my place, but Darin's comments are not applied in the patch you uploaded for landing. Also, in WebKit2/ChangeLog, file/function changes are written 3 times. I think you may have uploaded the wrong patch.
Hyowon Kim
Comment 7
2014-04-14 19:15:23 PDT
Created
attachment 229336
[details]
patch for landing
Hyowon Kim
Comment 8
2014-04-14 19:16:33 PDT
(In reply to
comment #6
)
> (In reply to
comment #4
) > > Created an attachment (id=229270) [details] [details] > > patch for landing > > This may not be my place, but Darin's comments are not applied in the patch you uploaded for landing. > Also, in WebKit2/ChangeLog, file/function changes are written 3 times. > > I think you may have uploaded the wrong patch.
Thank you for letting me know.
WebKit Commit Bot
Comment 9
2014-04-15 19:04:28 PDT
Comment on
attachment 229336
[details]
patch for landing Clearing flags on attachment: 229336 Committed
r167340
: <
http://trac.webkit.org/changeset/167340
>
WebKit Commit Bot
Comment 10
2014-04-15 19:04:35 PDT
All reviewed patches have been landed. Closing bug.
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