add a flag to HitTestRegion::flags for extended hit-test area |
||||||
Issue descriptionClients can specify an extended area for hit-test so they can receive events even though event location is in_non_client_area. Need to add a flag to HitTestRegion::flags for this so that if this flag is set, we dispatch events to the root (the first element in the aggregated list). Valery, do you want to work on adding the flag when preparing hit-test-data? And I can change HitTestQuery to use this flag to find the target after this flag is set?
,
Aug 15 2017
BrowserNonClientFrameViewMus::UpdateClientArea() (https://cs.chromium.org/chromium/src/chrome/browser/ui/views/frame/browser_non_client_frame_view_mus.cc?type=cs&sq=package:chromium&l=177) seems to set additional client areas as well.
,
Aug 15 2017
,
Oct 20 2017
Not sure if this needs a flag or could be acomplished by setting a hit test region on a window and a dedicated resizer, similar to how shaped app windows are doing that.
,
Feb 26 2018
,
Apr 24 2018
Migrating Proj-Mustash-Mus to components Internals>Services>WindowService and Internals>Services>Ash
,
Aug 14
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by varkha@chromium.org
, Aug 15 2017