New issue
Advanced search Search tips

Issue 659932 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Incorrect data is returned on display getInfo

Reported by suhassha...@gmail.com, Oct 27 2016

Issue description

Chrome Version: 53.0.2785.154 (Official Build) (64-bit)
Chrome OS Version: 8530.96.0 (Official Build) stable-channel panther
Chrome OS Platform: Asus Chrome box
Network info: -NA-


Issue 1:
Steps To Reproduce:
chrome.system.display.onDisplayChanged.addListener is triggered more than once when there is a change in display settings for e.g. changing to unified desktop mode.

Expected Result: Would be nice if the event is triggered only once

Actual Result: Event is triggered more than once


 Issue 2 :
Steps To Reproduce:
chrome.system.display.getInfo gives same display information for both workArea and bounds.

Expected Result: WorkArea should exclude chrome os taskbar (width&height) and bounds should include it.

Actual Result: WorkArea includes chrome os taskbar.


 Issue 3 :
Steps To Reproduce:
In unified desktop mode, change the shelf position of taskbar to left/right.

Expected Result: Updated workArea in display.getInfo.

Actual Result: WorkArea is just the monitor bounds.


 Issue 4 :
Steps To Reproduce:
1. In unified desktop mode, change the shelf position of taskbar to left/right.
2. Switch from unified mode to normal multimonitor mode by unchecking 'Windows can span displays'.
3. Change the display orientation. (Keep Monitor 1 above Monitor 2).
4. Switch back to unified desktop mode by checking 'Windows can span displays'.

Expected Result: Shelving the chrome os taskbar to left/right works fine.

Actual Result: Chrome OS taskbar cannot be shelved to left/right. Cannot revert this behavior even after reverting display settings or restarting the machine.

A zip file of sample chromeapp is attached. 
 
Display.zip
5.8 KB Download
Note that screen.width, screen.height, screen.availWidth etc are adjusted correctly. It also appears that new bounds are set to latest only after a slight delay.

Comment 2 by vsu...@chromium.org, Jan 26 2017

Components: OS>Kernel>Video
Status: Untriaged (was: Unconfirmed)
Components: -OS>Kernel>Video OS>Kernel>Graphics

Comment 4 by vsu...@chromium.org, Jan 26 2017

Status: Unconfirmed (was: Untriaged)
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 13 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment