|
|
Chromium Code Reviews
DescriptionRefactor ZoomControlsDelegate out of ContentViewCore
We can keep this logic entirely in AwContents, it doesn't need to be in
ContentViewCore. I'm using the existing GestureStateListener interface to signal
AwZoomControls of the relevant events, but I did have to add a few more events
to that interface. Hopefully they're OK and will work with our future plans to
refactor more input-handling stuff out of ContentViewCore.
Note on testing this: the Android WebView shell works for testing but I had to
knock out the "&& mAwContents.getSettings().shouldDisplayZoomControls()" check
in getZoomController() to enable the zoom controls. Once you do this they appear
when scrolling.
BUG=664339
Committed: https://crrev.com/6ea15211ce9bda01f3ef0a014d30997b5fe06769
Cr-Commit-Position: refs/heads/master@{#438045}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Don't unnecessarily route detach/visibility change events through CVC and back #
Total comments: 4
Patch Set 3 : Remove more stuff #Patch Set 4 : Rebase (no actual changes needed) #
Messages
Total messages: 37 (21 generated)
The CQ bit was checked by rlanday@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
rlanday@chromium.org changed reviewers: + aelias@chromium.org, boliu@chromium.org, jinsukkim@chromium.org
rlanday@chromium.org changed required reviewers: + boliu@chromium.org
I think this works, still waiting for the trybots to run but the zoom controls worked fine on my test device
On 2016/12/08 at 01:52:25, rlanday wrote: > I think this works, still waiting for the trybots to run but the zoom controls worked fine on my test device aelias suggested that we should look at the other GestureEventListener instances and try to figure out if GestureEventListener is something we want to keep around or if it too can be refactored into something cleaner
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)
https://codereview.chromium.org/2561463004/diff/1/content/public/android/java... File content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java (right): https://codereview.chromium.org/2561463004/diff/1/content/public/android/java... content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java:81: public void onVisibilityChanged(int visibility) {} visibility and detach are signals *from* the embedder, in webview's case, from AwContents, there is no need to tell embdder about these
https://codereview.chromium.org/2561463004/diff/1/content/public/android/java... File content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java (right): https://codereview.chromium.org/2561463004/diff/1/content/public/android/java... content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java:81: public void onVisibilityChanged(int visibility) {} On 2016/12/08 at 06:08:05, boliu wrote: > visibility and detach are signals *from* the embedder, in webview's case, from AwContents, there is no need to tell embdder about these Oh cool, let me clean this up...
The CQ bit was checked by rlanday@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
I cleaned this up as requested, the ScreenOrientationListenerTest that was failing on the trybot is passing on my test device
https://codereview.chromium.org/2561463004/diff/20001/android_webview/java/sr... File android_webview/java/src/org/chromium/android_webview/AwContents.java (right): https://codereview.chromium.org/2561463004/diff/20001/android_webview/java/sr... android_webview/java/src/org/chromium/android_webview/AwContents.java:3247: if (!viewVisible) { I was gonna suggest move this to where we call CVC.onVisibilityChanged, but webview never actually call that method! it was dead code! so just remove this as well https://codereview.chromium.org/2561463004/diff/20001/content/public/android/... File content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java (right): https://codereview.chromium.org/2561463004/diff/20001/content/public/android/... content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java:78: * Called when the gesture source (ContentViewCore)'s containing view's remove these two?
The CQ bit was checked by rlanday@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Updated with requested changes https://codereview.chromium.org/2561463004/diff/20001/android_webview/java/sr... File android_webview/java/src/org/chromium/android_webview/AwContents.java (right): https://codereview.chromium.org/2561463004/diff/20001/android_webview/java/sr... android_webview/java/src/org/chromium/android_webview/AwContents.java:3247: if (!viewVisible) { On 2016/12/08 at 21:29:07, boliu wrote: > I was gonna suggest move this to where we call CVC.onVisibilityChanged, but webview never actually call that method! it was dead code! > > so just remove this as well Oh interesting https://codereview.chromium.org/2561463004/diff/20001/content/public/android/... File content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java (right): https://codereview.chromium.org/2561463004/diff/20001/content/public/android/... content/public/android/java/src/org/chromium/content_public/browser/GestureStateListener.java:78: * Called when the gesture source (ContentViewCore)'s containing view's On 2016/12/08 at 21:29:07, boliu wrote: > remove these two? oops
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm think I meant to do that 2 days ago..
The CQ bit was checked by rlanday@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from boliu@chromium.org Link to the patchset: https://codereview.chromium.org/2561463004/#ps60001 (title: "Rebase (no actual changes needed)")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) chromeos_amd64-generic_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by rlanday@chromium.org
I tried some of the failing tests on master, they're failing there too, hopefully they'll start working soonish...
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by rlanday@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 60001, "attempt_start_ts": 1481598270497380,
"parent_rev": "82e4fd0520cd68c843125b868f5e4fbaa876ef50", "commit_rev":
"fabfe51366d0ed75649495135316a2437888ec74"}
Message was sent while issue was closed.
Description was changed from ========== Refactor ZoomControlsDelegate out of ContentViewCore We can keep this logic entirely in AwContents, it doesn't need to be in ContentViewCore. I'm using the existing GestureStateListener interface to signal AwZoomControls of the relevant events, but I did have to add a few more events to that interface. Hopefully they're OK and will work with our future plans to refactor more input-handling stuff out of ContentViewCore. Note on testing this: the Android WebView shell works for testing but I had to knock out the "&& mAwContents.getSettings().shouldDisplayZoomControls()" check in getZoomController() to enable the zoom controls. Once you do this they appear when scrolling. BUG=664339 ========== to ========== Refactor ZoomControlsDelegate out of ContentViewCore We can keep this logic entirely in AwContents, it doesn't need to be in ContentViewCore. I'm using the existing GestureStateListener interface to signal AwZoomControls of the relevant events, but I did have to add a few more events to that interface. Hopefully they're OK and will work with our future plans to refactor more input-handling stuff out of ContentViewCore. Note on testing this: the Android WebView shell works for testing but I had to knock out the "&& mAwContents.getSettings().shouldDisplayZoomControls()" check in getZoomController() to enable the zoom controls. Once you do this they appear when scrolling. BUG=664339 Review-Url: https://codereview.chromium.org/2561463004 ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Description was changed from ========== Refactor ZoomControlsDelegate out of ContentViewCore We can keep this logic entirely in AwContents, it doesn't need to be in ContentViewCore. I'm using the existing GestureStateListener interface to signal AwZoomControls of the relevant events, but I did have to add a few more events to that interface. Hopefully they're OK and will work with our future plans to refactor more input-handling stuff out of ContentViewCore. Note on testing this: the Android WebView shell works for testing but I had to knock out the "&& mAwContents.getSettings().shouldDisplayZoomControls()" check in getZoomController() to enable the zoom controls. Once you do this they appear when scrolling. BUG=664339 Review-Url: https://codereview.chromium.org/2561463004 ========== to ========== Refactor ZoomControlsDelegate out of ContentViewCore We can keep this logic entirely in AwContents, it doesn't need to be in ContentViewCore. I'm using the existing GestureStateListener interface to signal AwZoomControls of the relevant events, but I did have to add a few more events to that interface. Hopefully they're OK and will work with our future plans to refactor more input-handling stuff out of ContentViewCore. Note on testing this: the Android WebView shell works for testing but I had to knock out the "&& mAwContents.getSettings().shouldDisplayZoomControls()" check in getZoomController() to enable the zoom controls. Once you do this they appear when scrolling. BUG=664339 Committed: https://crrev.com/6ea15211ce9bda01f3ef0a014d30997b5fe06769 Cr-Commit-Position: refs/heads/master@{#438045} ==========
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/6ea15211ce9bda01f3ef0a014d30997b5fe06769 Cr-Commit-Position: refs/heads/master@{#438045} |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
