RESOLVED FIXED 49396
Make WebWidget actively notify client when compositing enables
https://bugs.webkit.org/show_bug.cgi?id=49396
Summary Make WebWidget actively notify client when compositing enables
Nat Duca
Reported 2010-11-11 11:55:15 PST
Right now, RenderWidget pasively determines when compositing enables based on checking isAcceleratedCompositingActive. This patch adds active notification for when compositing enables and disables.
Attachments
Proposed patch (2.85 KB, patch)
2010-11-11 12:05 PST, Nat Duca
fishd: review-
Round 2 (5.44 KB, patch)
2010-11-15 12:03 PST, Nat Duca
no flags
Better name (5.34 KB, patch)
2010-11-15 14:12 PST, Nat Duca
no flags
Nat Duca
Comment 1 2010-11-11 12:05:55 PST
Created attachment 73633 [details] Proposed patch
Darin Fisher (:fishd, Google)
Comment 2 2010-11-12 16:26:33 PST
Comment on attachment 73633 [details] Proposed patch View in context: https://bugs.webkit.org/attachment.cgi?id=73633&action=review > WebKit/chromium/src/WebViewImpl.cpp:2383 > + m_layerRenderer->finish(); // finish all GL rendering before we hide the window? TODO(nduca) fixthisshit TODO(nduca) -> FIXME and leave a more descriptive comment for someone else who may be reading this code. > WebKit/chromium/src/WebViewImpl.cpp:2390 > + m_layerRenderer->resizeOnscreenContent(WebCore::IntSize(std::max(1, m_size.width), no need for the WebCore prefix. > WebKit/chromium/public/WebWidgetClient.h:54 > + virtual void didChangeAcceleratedCompositingActive(bool active) { } nit: how about didActivateAcceleratedCompositing(bool)?
Nat Duca
Comment 3 2010-11-15 12:03:25 PST
Created attachment 73919 [details] Round 2
Darin Fisher (:fishd, Google)
Comment 4 2010-11-15 13:57:17 PST
Comment on attachment 73919 [details] Round 2 View in context: https://bugs.webkit.org/attachment.cgi?id=73919&action=review > WebKit/chromium/src/WebViewImpl.cpp:-1022 > - m_layerRenderer->present(); nice to see this cleanup! > WebKit/chromium/public/WebWidgetClient.h:54 > + virtual void didAcceleratedCompositingEnable(bool active) { } why this over didActivateAcceleratedCompositing? when vangelis added the isAcceleratedCompositingActive, i suggested using "enabled" instead of "active" as the suffix, but he argued against "enable" since that sounds like the compile-time option (is the code enabled at all). so, we went with "active", and he used that throughout the codebase (both webkit and chrome). can we stick with "active"/"activate"?
Nat Duca
Comment 5 2010-11-15 14:06:33 PST
> why this over didActivateAcceleratedCompositing? My bad. I made this change last Friday before I got your emailed ocmmets; the name I jotted down on the post-it was different. Will upload a new patch shortly.
Nat Duca
Comment 6 2010-11-15 14:12:55 PST
Created attachment 73929 [details] Better name
WebKit Commit Bot
Comment 7 2010-11-15 21:13:01 PST
Comment on attachment 73929 [details] Better name Clearing flags on attachment: 73929 Committed r72058: <http://trac.webkit.org/changeset/72058>
WebKit Commit Bot
Comment 8 2010-11-15 21:13:07 PST
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.