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

Issue 808564 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Layout Issue Since Recent Upgrade to Chrome 63 or 64

Reported by icandi...@gmail.com, Feb 2 2018

Issue description

<b>Chrome Version       : <Copy from: 'about:version'></b>
OS Version: OS X 10.9.2
URLs (if applicable) : http://best-nest-test.myshopify.com
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: OK
    Firefox: OK
    IE/Edge: N/A

What steps will reproduce the problem?
1. Open the page
2.
3.

What is the expected result?

See screenshot #1.


What happens instead of that?

See screenshot #2


Please provide any additional information below. Attach a screenshot if
possible.

I've added a two-column, responsive slider section on a client's website which, for a number of reasons, uses display: table, table-row and table-cell. It looks great in FF and Safari, and used to look great in Chrome.

Recently the client contacted me to say the second column in the slider section appeared "squished," and sure enough, it does. It seems the second column takes its height from the initial page load, then the rest of the section is drawn—to its full height—but the second column stays as short as it was initially.

I've attached two screenshots, and here's a link: http://best-nest-test.myshopify.com

I've tried a number of different things since finding out about the problem the other day—and setting things up this way was a last resort, I did try other ways of displaying the divs. I've got dynamic content, responsive content, text and buttons in the two right column containers. I may have overlooked some small thing, but it's unlikely… besides, it used to work just fine.

Is there a fix, or is this a bug?!

BTW, this is an Official Build of 64 I'm using, version 64.0.3282.119. It was reproduced by a Chrome forum user, though he says it's fixed in Canary 66.

 
Screen Shot 2018-02-01 at 3.46.35.png
1.9 MB View Download
Screen Shot 2018-02-01 at 2.15.14.png
1.4 MB View Download

Comment 1 by lgrey@chromium.org, Feb 2 2018

Components: Blink

Comment 2 by woxxom@gmail.com, Feb 3 2018

* Broken in in 63.0.3237.0

  Bisect info: 507423 (good) - 507447 (bad)
  https://chromium.googlesource.com/chromium/src/+log/de26e42d..08ea271b?pretty=fuller
  Suspecting r507427 = 65d9417940fca2d9edc013f02dbc5ba3b7cccc3c = https://crrev.com/c/700520 by robhogan@gmail.com
  "Treat percent height cells with nothing to resolve against as auto"
  Landed in 63.0.3237.0

* Fixed in 65.0.3318.0

  Bisect info: 528141 (bad) - 528157 (good)
  https://chromium.googlesource.com/chromium/src/+log/a3ba62ce..4429ca25?pretty=fuller
  Suspecting r528156 = 9e7701a83830e5e68640af9dbb5932c73cf74ef3 = https://crrev.com/c/858017 by robhogan@gmail.com
  "Revert "Treat percent height cells with nothing to resolve against as auto""
  Landed in 65.0.3318.0
Labels: Needs-Milestone Needs-Bisect
Cc: sc00335...@techmahindra.com
Components: -Blink Blink>Layout
Labels: -Type-Bug -Pri-3 -Needs-Bisect ReleaseBlock-Stable Triaged-ET M-64 FoundIn-64 Target-64 hasbisect OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: robho...@gmail.com
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on reported version 64.0.3282.119 and on latest stable 64.0.3282.140 but fixed on latest dev 65.0.3325.31 and latest canary 66.0.3339.0 using Mac 10.13.3,Ubuntu 14.04 and Windows 10.

Suspecting Reviewed-on: https://chromium-review.googlesource.com/858017 from above comment.

@robhogan: Please confirm whether this fix is safe to merge to M-64? Adding RB-Stable for M-64. Please change if not the case.

Thanks!


Labels: OS-Chrome
Able to reproduce the issue on 64.0.3282.144/10176.68.0 - Peppy

Comment 6 by e...@chromium.org, Feb 6 2018

Status: WontFix (was: Assigned)
This was an intentional revert as it caused a more serious breakage. The change will return once the latest regression has been addressed.

Comment 7 by woxxom@gmail.com, Feb 6 2018

#6, the question was different - is it possible to merge the revert to M64.

Sign in to add a comment