| commit | 64ce91b15c91a25f3088c94830b6416f9dcf5224 | [log] [tgz] |
|---|---|---|
| author | Jason Gerecke <jason.gerecke@wacom.com> | Fri Jun 04 21:32:08 2021 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 04 21:32:08 2021 |
| tree | 3583ecf8d0c14d3a6bf7dc6914e9616de43ea196 | |
| parent | 392830f38b340de303c756aa6312cf2013b93eae [diff] |
ash: Allow stylus tools palette to appear on external pen-capable displays External pen-capable displays like the "Wacom One" allow the use of a stylus with Chromebooks which may not have their own built-in pen digitizer. We should allow the stylus tools palette to appear on such displays so that the user may access its tools. Making this happen is as simple as allowing external (USB) pen-capable displays to satsfy the HasStylusInput() check and then relaxing the requirement for an internal display to just a stylus display. We also have to be careful to ensure that pen insertion/removal events only trigger the stylus tools bubble on the internal display, if present. We add a pair of new unit tests to validate the stricter requirements on when insertion/removal may trigger the bubble. Bug: b:183214775 Test: ash_unittests --gtest_filter="*"; new unit tests Change-Id: I1b34f413b3904e99eee427dad424139a4df0cf0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2868022 Commit-Queue: Harry Cutts <hcutts@chromium.org> Reviewed-by: Ahmed Mehfooz <amehfooz@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#889462}
ChromiumChromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.