Browser window does not set large enough minimum size, allows top and bottom toolbar contents to overlap strangely
Reported by
jshan...@etouch.net,
Jun 22 2016
|
||||||||||
Issue descriptionChrome Version: 52.0.2743.49 (Official Build) 01329c89b0a4e83f6481fd5f600b520719a25c9f-refs/branch-heads/2743@{#441}-32/64 bit OS: Windows(7,8,8.1,10), , Linux (ubuntu 14.04 LTS) Steps: 1. Launch Chrome and navigate to chrome://version 2. Download the page using 'Save as' option of context menu and resize the browser window horizontally upward. 3. Observe download bar. Actual: Weird overlapping of download bar and ominibox is observed after resizing browser window horizontally upward. Expected: No such overlapping should be seen after resizing browser window horizontally upward. This is a regression issue broken in M-50, below is bisect info Good Build: 50.0.2631.0 Bad Build: 50.0.2633.3 Narrow Bisect: https://chromium.googlesource.com/chromium/src/+log/1e12ce9f124828d724656a8e113213acc39aa9cc..006b75cf40c873bcc386bf1ba99b8b63bc1818e9?pretty=fuller&n=100 Suspecting: r371699 ? Please help to re-assign if your change is not the cause for this issue. Note: This issue is not seen on Mac OS.
,
Jun 23 2016
That regression range seems to be wrong. I run binary bisect, but 372647 didn't have this issue. jshanbal@, can you run bisect again? +estade@, pkasting@ who may have an idea.
,
Jun 23 2016
this is clearly because of the layers we've been adding, but do we really care what the browser looks like at this size? Why is it even possible to resize it this way? assigning to pkasting for triage.
,
Jun 24 2016
With response to comment #2, re-bisected again on different machine and getting bisect range as given below. Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/9a1c85fb7079ce5ffc249c4a787058c81dccdd31..7f7eb25a8abd2d173c5ae1fe95d92e398cf70267?pretty=fuller&n=100 Suspecting: r371511 ?
,
Jun 29 2016
The browser should compute a minimum necessary size (generally in a GetMinimumSize() override), which will prevent the user from sizing it small enough to make things look broken. So yes, this is a real bug that we should fix.
,
Jul 3 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 3 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 3 2017
Still repros
,
Jul 4
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 5
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by cbiesin...@chromium.org
, Jun 22 2016Owner: ----
Status: Untriaged (was: Assigned)