Chrome rendering bug in version 54
Reported by
t...@driveback.ru,
Oct 28 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36 Steps to reproduce the problem: 1. open anonymous mode. 2. open https://aizel.ru/?driveback_test_mode=1 3. try to leave the site What is the expected behavior? you must see full lightbox What went wrong? Chrome cut the half of the image Did this work before? N/A Does this work in other browsers? Yes Chrome version: 54.0.2840.71 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0 This bug is only in Chrome v 54. It happened in iframes. Sometimes it is working, sometimes it cuts just left side of the iframe, sometimes it cuts the top. It happens on all websites, which use iframes: aizel.ru, quelle.ru, izobility.com.
,
Oct 29 2016
I can reproduce using Chrome 54 as well as using the latest canary - 56.0.2903.0, on Windows 7. I am guessing this is a regression.
,
Oct 29 2016
We changed our source code and you won't be able to reproduce this bug. The problem was, that all iframes was rendered with css style visibility:hidden. It was rendered incorrectly. We changed css to display:none and it work fine now. But I think this bug will affect a lot of websites, because lots of developers render their components with visibility:hidden.
,
Oct 29 2016
#3 - can you maybe, please, change it back to the old code for a moment, save it as a self contained ZIP that reproduces the issue and attach it here? That would make reproducing in the future and bisecting much much easier... Thank you.
,
Oct 31 2016
,
Nov 7 2016
We would still like feedback with a reproduction case. However, this seems serious, so I'll try to fiddle with the site to recreate the problem.
,
Nov 21 2016
,
Nov 21 2016
I can't even get the lightbox to show. Developer, please help us out with a current version that we can load which shows the bug, with complete reproduction instructions. Otherwise we'll have to close the bug. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dtapu...@chromium.org
, Oct 28 2016