Issue metadata
Sign in to add a comment
|
Rendering issue on twitter
Reported by
regis.ca...@gmail.com,
Apr 28 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3409.2 Safari/537.36 Example URL: https://twitter.com Steps to reproduce the problem: 1. open some tweet with answers (I used https://twitter.com/innocent/status/989444299124297729 for the demo) 2. scroll down What is the expected behavior? everything is readable What went wrong? some clipping occurs (see demo video) Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? Yes previous dev version was fine AFAIK Does this work in other browsers? N/A Chrome version: 68.0.3409.2 Channel: dev OS Version: ubuntu 17.10 / gnome shell (up to date) Flash Version: I can see some "BadWindow" warning in chrome://gpu Log Messages [7133:7265:0428/081030.523230:WARNING:x11_util.cc(1362)] : X error received: serial 11358, error_code 3 (BadWindow), request_code 4, minor_code 0 (Unknown) [7133:7265:0428/082153.869052:WARNING:x11_util.cc(1362)] : X error received: serial 35601, error_code 3 (BadWindow), request_code 4, minor_code 0 (Unknown) [7133:7133:0428/082203.412436:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1 [7133:7265:0428/082906.107803:WARNING:x11_util.cc(1362)] : X error received: serial 45444, error_code 3 (BadWindow), request_code 4, minor_code 0 (Unknown)
,
Apr 30 2018
,
Apr 30 2018
regis.caspar@ Thanks for the issue. Tested this issue on Ubuntu 17.10 and Windows 10 on the reported version 68.0.3409.2 and the latest Canary 68.0.3414.0 and unable to reproduce the issue. 1. Launched Chrome and navigated to the given link above. 2. On scrolling through the page, cannot observe any clipping on the page. Attached is the screen cast for reference. Request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Apr 30 2018
susan@ Hi, thanks for your answer. First test: guest session. -------------------------- Was able to reproduce on BBC's twitter account (guest.png and demo.mp4). Inspecting the dom the elements are there and even well detected by the inspector. When hovering some content appear. (I used a tweet with 500+ answers) The only flag I have "ON" that is not standard is "strict site isolation" Will try again with the flag reset to it's default.
,
Apr 30 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
,
Apr 30 2018
Second test: guest session. --------------------------- Using a new Ubuntu user, I did start Chrome, and tried again to reproduce (see attachment) using the BBC tweet. I still see the issue (no flag, no extension besides the gnome-shell one, new chrome profile) I hope that helps.
,
May 2 2018
regis.caspar@ Thanks for the update. Re-tested this issue on Ubuntu 17.10 on the reported version 68.0.3409.2 and the latest Canary build 68.0.3416.0 and unable to reproduce the issue as per comments #4 & #6. - Tried scrolling through the given URL in the original comment with "strict site isolation" flag enabled and unable to repro the issue. - Tried scrolling the page in a Guest Profile and unable to repro the issue. As per comment #1, as this issue is similar to issue 825280 , CC'ing the owner of the bug-chrishtr@ to help in further triaging of this issue. Thanks..
,
May 2 2018
,
May 2 2018
Hi Chris, I don't understand this bug merge. I did report 825280 and you did fix it (I was able to verify it was fixed), but there's some new similar issue or some regression in the dev version..
,
May 3 2018
Ok, re-opening.
,
May 4 2018
As per comment #3 & #7, as this issue is not reproducible at TE end, removing 'Needs-Bisect' label and requesting chrishtr@ to look into the issue and help in further triaging. Thanks..
,
May 5 2018
I can reproduce the bug. Investigating.
,
May 5 2018
Verified that reverting https://chromium.googlesource.com/chromium/src/+/e931d2aecb4d72946962e57e7e1586668071b504 fixes the bug; duplicate. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by regis.ca...@gmail.com
, Apr 28 2018