Issue metadata
Sign in to add a comment
|
"overflow: hidden;" doesn't prevent the blur and scale effect from exceeding its parent dimensions
Reported by
shaker.h...@nagwa.com,
Mar 20 2018
|
||||||||||||||||||||||||
Issue descriptionChrome Version : 65.0.3325.162 (Official Build) (64-bit) URLs (if applicable) : https://www.hindawi.org/ Other browsers tested: Firefox, Safari, Microsoft Edge Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: OK Firefox: OK Edge: OK What steps will reproduce the problem? (1) Open The URL provided (2) Hover over any thumbnail What is the expected result? The blur and scale effect shouldn't go out of its parent container with overflow: hidden. What happens instead? It used to work fine on the previous version (Version 64.0.3282.186 (Official Build) (64-bit)), but now the "overflow: hidden;" property doesn't work for some reason when you give it to the parent. Please provide any additional information below. Attach a screenshot if possible.
,
Mar 21 2018
,
Mar 22 2018
Unable to reproduce this issue on reported version 65.0.3325.162, on latest canary 67.0.3377.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.3. Same behavior is seen in M60 and M-64 64.0.3282.186. Attaching screencast for reference. @Reporter: Please check the video and let us know if we miss anything. Could you please explain the expected behavior with a video if possible. Also check the issue on fresh profile which do not have any apps/extensions. Any further info on reproducing this issue would help in further triaging of the issue. Thanks!
,
Mar 22 2018
Sorry for that, I had to use a hack to target only chrome to override this broken behavior, I included a video to show you how to reproduce this issue. And as you'll see in the video, Firefox has no issue and also was the last version of chrome.
,
Mar 22 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 22 2018
I can't reproduce this in 66.0.3359.45. Would you mind trying Chrome Canary to see if the fix is there for you? Could test please try to repro in M-65 using the steps in the video. Note that the content area must be at least 1025 pixel wide to see the filter/blur CSS for the object tag. This might have been caused by my replaced content overflow issue that primarily hit iframes. That is present in M-65 but not M-66.
,
Mar 22 2018
Confirmed present on Mac 65.0.3325.106. Confirmed not present in M-67 Canary on Mac.
,
Mar 23 2018
Able to reproduce this issue on reported version 65.0.3325.162, on latest stable 65.0.3325.181 but fixed on latest beta 66.0.3359.45 and latest canary 67.0.3378.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.3. Hence providing reverse bisect info. Last Bad Build: 66.0.3350.0 First Good Build: 66.0.3352.0 You are probably looking for a change made after 537453 (known good), but no later than 537454 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/e282ebc6f0e5852cfc46ee688bae89a78d119270..0a9a5c311a1d3a298f952e495510bd6fe3faa2f6 Probably fixed by https://chromium-review.googlesource.com/923572. @ wangxianzhu: Please confirm the bug and help in re-assigning if is not related to your change. Please merge it to M-65 if we have any stable refresh. Adding RB-Stable for M-65. Please remove if not the case. Thanks!
,
Mar 23 2018
This is tricky. The Slimming Paint v1.75 change was reverted for M-66, so in theory the bug is still present in the M-66. It would be fixed for M-67. wangxianzhu@, what revision disabled SP 1.75 on trunk, so we can bisect around this? Or maybe test with explicit SP 1.75 disabled. Is that possible?
,
Mar 24 2018
Reduced test case. A svg object is needed. Seems to related to the iframe clip issue. The revisions that enabled or disabled SlimmingPaintV175: r537454: enabled r539401: disabled r543291: enabled again The beta branch point is r540276 which is after SlimmingPaintV175 was disabled, so there might be some other CL fixed the issue in beta. Checking.
,
Mar 24 2018
Bisected locally in the beta branch, and found that https://chromium-review.googlesource.com/c/chromium/src/+/958983 fixed the bug. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Mar 20 2018