Issue metadata
Sign in to add a comment
|
Some system UI components don't respect the display workarea when modified by the docked magnifier |
||||||||||||||||||||||
Issue descriptionChrome Version:67.0.3396.0/10575.3.0 dev channel Candy,Reks,Peppy OS:Chrome OS What steps will reproduce the problem? (1)Recover build >>In OOBE screen,Connect to a network (2)Enable Docked Magnifier from Accessibility (3)Go to 'Sign into your Chromebook' screen and observe Actual: Unable to view the Email field when entering an Email Expected: Should be able to view the email field while entering some text Raising this as Non-regression issue as the feature is newly implemented in M-67 Note:Issue is not seen for Linux,Windows OS Attached the screencast for reference..
,
Apr 17 2018
I don't know how magnifier is expected to work. Could you suggest what we could change here?
,
Apr 17 2018
Expected: I recommend to view the Email text field at least when entering some text Actual:Unable to view the Email field when editing.
,
Apr 17 2018
Magnifier changes the display's workarea [1] in the same way the shelf, and the chromevox panel do. Effectively reducing the height of the available area for windows. Windows should respect that, so instead of basing your window size on the full size of the display, you can base it on the workarea size. You can use the WorkAreaWatcherObserver [2]. [1]: https://cs.chromium.org/chromium/src/ui/display/display.h?type=cs&q=display::Display::work_area&l=120 [2]: https://cs.chromium.org/chromium/src/ui/base/work_area_watcher_observer.h?type=cs&q=Workareachange&l=17
,
Jul 18
,
Aug 20
,
Sep 6
,
Sep 6
This is now the master bug for these issues across the UI. Relevant bugs that aren't merged yet, please consider merging: 868625 868623 865795 865792
,
Sep 6
,
Sep 6
,
Sep 6
,
Sep 6
,
Sep 6
,
Sep 6
The old title is wrong. Docked magnifier changes the workarea, some other system components don't respect the modified workarea
,
Sep 6
Thanks for that update and clarification, afakhry@. Please let me know if you feel that all these bugs should be merged as dupes. Otherwise, I'll just leave this as the master blocking bug.
,
Sep 19
,
Sep 26
,
Sep 28
,
Oct 16
Jacob, could you help finding owner for this?
,
Oct 16
alemate@ this should be easy to fix for OOBE, just listen to display::DisplayObserver::OnDisplayMetricsChanged() for DISPLAY_METRIC_WORK_AREA and update your bounds according to the current display's Display::work_area().
,
Nov 19
,
Nov 27
,
Dec 1
,
Dec 1
,
Dec 1
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by afakhry@chromium.org
, Apr 16 2018Status: Assigned (was: Untriaged)