about:blank changes background color to same as adjacent tab
Reported by
underska...@gmail.com,
Apr 29 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.29 Safari/537.36 Example URL: about:blank; https://www.youtube.com/ Steps to reproduce the problem: 1. Open about:blank in a tab. I do it by ctrl+clicking a bookmark from the New Tab page. 2. Open a website (with a non-white bg color) in another tab. 3. Do stuff on the internet for a while. This includes opening and closing other tabs, opening and closing other windows, but not looking at (i.e. selecting) the about:blank tab. 4. Select the tab from step 2 by clicking on it. 5. Select the about:blank tab. What is the expected behavior? The about:blank page is white. What went wrong? The about:blank page has the same background color as the tab from step 2. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 59.0.3071.29 Channel: beta OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This isn't really that reproducible, but it has happened today and yesterday, and I've never seen it before that.
,
May 8 2017
i came across with the same issue. I couldnt record a screentcast. But i can say this issue is reproducable for me too.
,
May 9 2017
As far as I can see in the video in comment #1, you did it correctly, and the bug was reproduced. The background color of the about:blank page appears to be #ffffff in the beginning of the video, and #f1f1f1 near the end. The background color of youtube.com is #f1f1f1.
,
May 9 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 12 2017
Adding appropriate label to get more inputs on this issue. Thanks,
,
Sep 28 2017
Tested this issue using Chrome version #61.0.3163.100 and #63.0.3226.0 on Win 7. Unable to reproduce this issue as per the steps mentioned. @underskatten: Please find the attached screen cast and could you please try to upgrade your browser to latest version and let us know if the issue still persists. Thanks in Advance!!
,
Sep 29 2017
Unable to reproduce in Chrome 62.0.3202.38 beta (64-bit). Is there any way to get an old version of Chrome to test on, to check if I'm testing it correctly?
,
Sep 29 2017
Thank you for providing more feedback. Adding requester "rkalavakuntla@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 29 2017
>Is there any way to get an old version of Chrome 1. use the unofficial Chrome portable https://sourceforge.net/projects/portableapps/files/Google%20Chrome%20Portable/ 2. use the official Chromium (not Chrome) snapshots https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html * To find a snapshot number for the given version, use https://omahaproxy.appspot.com/ * To find where the regression appeared, use https://www.chromium.org/developers/bisect-builds-py
,
Sep 30 2017
I tried several versions of both 1. and 2. (including Chromium 59.0.3071.29). Unable to reproduce in any of them. I'm not sure if I'm doing it wrong, or there is something else going on.
,
Oct 5 2017
As per comment#10 this issue is not reproducible. Hence marking this as Wont-fix. @Reporter: Please feel free to re-open this issue or raise a new one if issue is seen again. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sandeepkumars@chromium.org
, May 8 201710.8 MB
10.8 MB View Download