Issue metadata
Sign in to add a comment
|
Bug on overflow hidden when embedding video (youtube/vimeo)
Reported by
spabr...@gmail.com,
Mar 20 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0 Steps to reproduce the problem: 1. Open the testcase.html 2. You see that the videos (iframes) are overlaying the parent container 3. What is the expected behavior? The video embeds should not be overlaying the parent container and be 'cutted' because of the overflow:hidden rule. What went wrong? You see that the first container contains a youtube iframe and is bigger than the container, but with overflow:hidden it shouldn't be visible and 'cutted' on the sites. But google chrome is not able to do this anymore (all other browsers works fine). The last container just contains a normal page and there the hidden overflow works well, so I guess it's somehow related to video embeds (vimeo embeds = the same issue). Did this work before? Yes Does this work in other browsers? Yes Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: OS X 10.13 Flash Version: Shockwave Flash 29.0 r0
,
Mar 21 2018
Able to reproduce the issue on chrome version 65.0.3325.162 and the same is not seen on latest canary 67.0.3375.0 using Windows 10, Ubuntu 14.04, Mac 10.12.6 hence providing reverse bisect info 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). https://chromium.googlesource.com/chromium/src/+log/e282ebc6f0e5852cfc46ee688bae89a78d119270..0a9a5c311a1d3a298f952e495510bd6fe3faa2f6 Reviewed on: https://chromium-review.googlesource.com/923572 @Xianzhu Wang: Please confirm the issue and help in re-assigning if it is not related to your change, please merge it to M-65. Adding ReleaseBlock-Stable as it seems recent break, feel free to remove it if not applicable. Thanks!
,
Mar 21 2018
The fixing CL is enabling a feature that that has been disabled in M66 and will be launched in M67. It's not possible to merge that into M65. Bisected to https://chromium.googlesource.com/chromium/src/+log/1a729f41637add03a9f79b8a1518a27faf175350..61e62a764dc2cfc43924100712682a1f3cbba37a. Suspecting https://chromium.googlesource.com/chromium/src/+/88986f832c463a210324d7d9cf9b5213f7b69f63. schenney@ do you think we should fix this in M65 (e.g. by reverting the CL)?
,
Mar 21 2018
The fix was very simple to merge back into M-65 if it's decided to do that. But given we've just pushed out another M-65, and there's now not that long to M-66, I am inclined to just leave things as they are for now. We would only merge it back at this point if a major site or a lot of sites are functionally broken.
,
Mar 21 2018
Thank you schenney@. Based on #4, we won't be blocking further M65 roll out for this.
,
Mar 22 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Mar 20 2018