New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 613828 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 2016
Cc:
rdevlin....@chromium.org
█ ashej...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature



Sign in to add a comment

windows API does not give access to screen information

Reported by arn...@bzzt.net, May 21 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
When implementing an extension with the 'windows' API, no information about the screen containing the window is available.

What is the expected behavior?

What went wrong?
I wanted to write an extension that takes into account the resolution of the screen (not the width of the window), but couldn't.

Did this work before? N/A 

Chrome version: 49.0.2623.75  Channel: n/a
OS Version: Debian
Flash Version: Shockwave Flash 20.0 r0

Comment 1 by msrchandra@chromium.org, May 23 2016

Labels: Te-NeedsFurtherTriage

Comment 2 by ashej...@chromium.org, Jul 5 2016

Cc: ashej...@chromium.org
Components: Platform>Extensions>API
Labels: -Te-NeedsFurtherTriage
Status: Untriaged (was: Unconfirmed)
Marking the above as Untriaged as this is a feature request.

Dev team will take a final call on the above request.

Thank you!

Comment 3 by rdevlin....@chromium.org, Jul 8 2016

Cc: rdevlin....@chromium.org
Status: WontFix (was: Untriaged)
Windows and Display are two separate components, and the API shouldn't conflate the two.  We have the chrome.system.display API for reading display information.

Comment 4 by arn...@bzzt.net, Jul 13 2016 

That's exactly what I needed, thanks, sorry for the noise!
►

Sign in to add a comment