|
|
Created:
4 years, 2 months ago by Elliot Glaysher Modified:
4 years, 2 months ago CC:
chromium-reviews, tfarina Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
Descriptionmus: Use TooltipManagerAura in NativeWidgetMus.
mash now shows tooltips on hover over items.
BUG=599558
Committed: https://crrev.com/1b3d5f1878974c14c21a29a13a93ef630c74d1f6
Cr-Commit-Position: refs/heads/master@{#422562}
Patch Set 1 #Patch Set 2 : Try readding the unit tests. #Patch Set 3 : Actually put that file in the right spot. #
Total comments: 3
Patch Set 4 : [xxx] dont commit; for trybot run only. #Patch Set 5 : [xxx] more hacks to see if this is viable #Patch Set 6 : [xxx] Does switching to CreatePlatformDesktopNativeWidgetImpl fix it? #Patch Set 7 : add namespace #Patch Set 8 : Remove theoretically unneeded screen now. #Patch Set 9 : Of course there's a second, different test suite in the same file. Why would I ever have thought ot… #
Messages
Total messages: 42 (29 generated)
The CQ bit was checked by erg@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...
The CQ bit was checked by erg@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...
The CQ bit was checked by erg@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...
erg@chromium.org changed reviewers: + jonross@chromium.org, sky@chromium.org
jonross: So I took a stab at this bug. The linked bug says that this will require mus integration, but direct integration of the aura code in the client appears to work just fine in mash. Is there some case here that I'm not thinking of that would require a dedicated TooltipControllerMus with mus server integration? sky: Review/owners
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
On 2016/09/29 22:34:06, Elliot Glaysher wrote: > jonross: So I took a stab at this bug. The linked bug says that this will > require mus integration, but direct integration of the aura code in the client > appears to work just fine in mash. Is there some case here that I'm not thinking > of that would require a dedicated TooltipControllerMus with mus server > integration? > > sky: Review/owners Having NativeWidgetMus install a TooltipController means each client is going to attempt to display tooltips. As each client doesn't necessarily see other client windows this could result in multiple clients attempting to show a tooltip at the same time for different windows because they think their window is visible under the cursor. I think ash needs to be responsible for handling showing of tooltips.
I think I'm wrong. I was worried tooltips would get confused by any observed pointerevents, but those are routed differently. So, I think this should just work. The only concern I have is does it work for renderwidgethostview? My understanding is each renderwidgethostviewmus has a ui::Window, but isn't contained in a widget.
https://codereview.chromium.org/2379073003/diff/40001/ui/views/BUILD.gn File ui/views/BUILD.gn (right): https://codereview.chromium.org/2379073003/diff/40001/ui/views/BUILD.gn#newco... ui/views/BUILD.gn:928: "corewm/tooltip_controller_unittest.cc", Can you make sure this test actually ends up creating a NativeWidgetMus? On a quick look I suspect it doesn't, but I could be wrong. https://codereview.chromium.org/2379073003/diff/40001/ui/views/mus/native_wid... File ui/views/mus/native_widget_mus.cc (right): https://codereview.chromium.org/2379073003/diff/40001/ui/views/mus/native_wid... ui/views/mus/native_widget_mus.cc:600: aura::client::SetTooltipClient(window_tree_host_->window(), NULL); nullptr
On 2016/09/30 15:15:31, sky wrote: > https://codereview.chromium.org/2379073003/diff/40001/ui/views/BUILD.gn > File ui/views/BUILD.gn (right): > > https://codereview.chromium.org/2379073003/diff/40001/ui/views/BUILD.gn#newco... > ui/views/BUILD.gn:928: "corewm/tooltip_controller_unittest.cc", > Can you make sure this test actually ends up creating a NativeWidgetMus? On a > quick look I suspect it doesn't, but I could be wrong. > > https://codereview.chromium.org/2379073003/diff/40001/ui/views/mus/native_wid... > File ui/views/mus/native_widget_mus.cc (right): > > https://codereview.chromium.org/2379073003/diff/40001/ui/views/mus/native_wid... > ui/views/mus/native_widget_mus.cc:600: > aura::client::SetTooltipClient(window_tree_host_->window(), NULL); > nullptr Ths bug referred to mus integration, as at the time there had been talk about having certain features are mus services, including tooltips. However if the current structure works I am in support of a simpler solution.
The CQ bit was checked by erg@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)
The CQ bit was checked by erg@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by erg@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...
The CQ bit was checked by erg@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...
The CQ bit was checked by erg@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...
The CQ bit was checked by erg@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
ptal https://codereview.chromium.org/2379073003/diff/40001/ui/views/BUILD.gn File ui/views/BUILD.gn (right): https://codereview.chromium.org/2379073003/diff/40001/ui/views/BUILD.gn#newco... ui/views/BUILD.gn:928: "corewm/tooltip_controller_unittest.cc", On 2016/09/30 15:15:30, sky wrote: > Can you make sure this test actually ends up creating a NativeWidgetMus? On a > quick look I suspect it doesn't, but I could be wrong. You're correct that this was wrong. I've moved two of the three test suites in this file from AuraTestBase to ViewsTestBase, and ported the native widget creation code to CreatePlatformDesktopNativeWidgetImpl(), which has different implementation in the ui/views/mus vs the base views code.
LGTM - did you make sure tooltips set on renderers work as well?
(Yes. Tested with the thumbnails on the NTP.)
The CQ bit was checked by erg@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #9 (id:160001)
Message was sent while issue was closed.
Description was changed from ========== mus: Use TooltipManagerAura in NativeWidgetMus. mash now shows tooltips on hover over items. BUG=599558 ========== to ========== mus: Use TooltipManagerAura in NativeWidgetMus. mash now shows tooltips on hover over items. BUG=599558 Committed: https://crrev.com/1b3d5f1878974c14c21a29a13a93ef630c74d1f6 Cr-Commit-Position: refs/heads/master@{#422562} ==========
Message was sent while issue was closed.
Patchset 9 (id:??) landed as https://crrev.com/1b3d5f1878974c14c21a29a13a93ef630c74d1f6 Cr-Commit-Position: refs/heads/master@{#422562}
Message was sent while issue was closed.
Excellent! On Mon, Oct 3, 2016 at 3:15 PM, <erg@chromium.org> wrote: > (Yes. Tested with the thumbnails on the NTP.) > > https://codereview.chromium.org/2379073003/ -- You received this message because you are subscribed to the Google Groups "Chromium-reviews" group. To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
Message was sent while issue was closed.
A revert of this CL (patchset #9 id:160001) has been created in https://codereview.chromium.org/2384083005/ by erg@chromium.org. The reason for reverting is: sky@ reports that TooltipControllerCaptureTest.Capture is failing on local chromeos builds.. |