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

Issue 596557 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome app's current window's innerbounds returns incorrect values

Reported by abo...@fusionlabs.net, Mar 21 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
1. Launch app
2. Connect to a machine
3. Notice, top and bottom are cut off by a few pixels
4. Drag window
5. Notice, window is made slightly larger, and black/white borders appear.  Window no longer changes content unless dragged again.

What is the expected behavior?
For this application's default options, once connected, window should remain the same size and not be resizeable.

What went wrong?
chrome.app.window.current().innerbounds is returning the wrong values.

Attached a demo app that reproduces and demonstrates issue, see ChromeTestInnerBounds.zip

In demo app, window is created at 800x600.  The resulting window's content is 784x561, while innerBounds returns 800x600.  Measuring with on-screen pixel ruler verifies incorrect results.  See attachment, ChromeTestInnerBounds-launchsizewithruler.png. Then re-sizing and locking min/max size continues to return incorrect values.

WebStore page: https://chrome.google.com/webstore/detail/chrome-rdp/cbkkbcmdlboombapidmoeolnmdacpkch

Did this work before? Yes 2/24/2016 - stable channel

Chrome version: 49.0.2623.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

Works correctly on ChromeOS 49.0.2623.95 and OSX 49.0.2623.95
 
ChromeTestInnerBounds.zip
1.9 KB Download
ChromeTestInnerBounds-launchsizewithruler.png
136 KB View Download

Comment 1 by dah...@chromium.org, Mar 21 2016

Cc: dah...@chromium.org
Project Member

Comment 2 by sheriffbot@chromium.org, Mar 22 2017

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