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

Issue 688605 link

Starred by 2 users
Status: Fixed
Merged: issue 576304
Owner:
skobes@chromium.org
Closed: Mar 2017
Cc:
█ dstockwell@chromium.org
rtoy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

change the CSS overflow from Scroll to Auto by JS doesn't affect the layout

Reported by csq1...@gmail.com, Feb 4 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. set the style overflow-y of a div to "scroll"
2. add an html element table into that div
3. set the width of the table to "100%"
4. when page loaded click a button to run a JavaScript
5. in that JS code set the overflow-y of the Div from "scroll" to "auto"

What is the expected behavior?
the width of the table inside the div should auto fit to "100%"

What went wrong?
the width of the table inside the div doesn't change

Did this work before? Yes the version before this version:56.0.2924.87 (64-bit)

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0
index.html
1.6 KB View Download

Comment 1 by krajshree@chromium.org, Feb 6 2017

Components: Blink>Layout
Labels: -Pri-2 hasbisect-per-revision M-57 OS-Linux Pri-1
Owner: skobes@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10 and Ubuntu 14.04 using reported version #56.0.2924.87 but the same is not reproducible in the latest canary #58.0.3003.0.

Unable to reproduce this issue on mac as after opening the attached index.html file, no scroll bar is seen.

Reverse Bisect Information:
=====================
Good build: 57.0.2928.0	Revision(433845)

Bad Build : 57.0.2929.0	Revision(434071)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/6d8345816cfb1b1f268ca4e2cf24a4e7f2f2c9af..4fc7dec0128b48b0f4d26d36e128a4d0c9d5d435

From the above change log possible CL that fixed this issue:

Review-Url: https://codereview.chromium.org/2523533002

skobes@ - Could you please check and merge the fix to M57 if it is a valid candidate.

Thanks...!!

Comment 2 by skobes@chromium.org, Feb 7 2017

Status: Fixed (was: Assigned)
Confirmed, this is fixed by r434018.

This change is already in M57, since it landed before the M57 branch cut.

Comment 3 by dstockwell@chromium.org, Feb 16 2017

Mergedinto: 576304
Status: Duplicate (was: Fixed)

Comment 4 by skobes@chromium.org, Feb 22 2017

Cc: dstockwell@chromium.org
Components: -Blink
Labels: M-56 Merge-Request-56
Status: Started (was: Duplicate)
Un-duping this from  issue 576304  since it regressed in M56 (culprit is r426807).

Requesting merge of r434018 into M56.

Comment 5 by skobes@chromium.org, Feb 22 2017

Cc: rtoy@chromium.org
 Issue 688377  has been merged into this issue.

Comment 6 by skobes@chromium.org, Feb 22 2017

Labels: OS-Android OS-Chrome OS-Mac OS-All

Comment 7 by skobes@chromium.org, Feb 22 2017

Labels: -OS-All

Comment 8 by skobes@chromium.org, Mar 8 2017

Status: Fixed (was: Started)

Comment 9 by amineer@chromium.org, Mar 9 2017

Labels: -Merge-Request-56
We're not shipping any more M56 builds.
►

Sign in to add a comment