Issue metadata
Sign in to add a comment
|
Regression : Background color of newly opened tab changes after switching between tabs.
Reported by
avsha...@etouch.net,
Jul 4 2017
|
||||||||||||||||||||
Issue descriptionChrome Version : 61.0.3148.0 (Official Build) 155b257ae4cf8873f8561ec6a00c61ebec47548a-refs/heads/master@{#484021} 32/64 bit OS : Windows(7,8,10), Linux(14.04 LTS) Test URL : https://msu.edu/~urban/sme865/resources/embedded_pdf.html What steps will reproduce the problem? 1. Launch chrome and navigate to above test URL. 2. Scroll down the page, right click on a link "urban@msu.edu" in the PDF file and select 'Open link in new tab' option (link opens in a new tab). 3. Now switch between both the tabs twice and observe the new tab opened in step 2. Actual Result : Unnecessarily background color of newly opened tab changes after switching between tabs. Expected Result : Instead, the background color of newly opened tab should remain white and should not change after switching between tabs. This is a regression issue broken in ‘M-60’, below is the Manual Regression range and will soon update other info. Good build : 60.0.3088.0 Bad build : 60.0.3089.0 Note : 1. Above issue is not seen in Mac(10.11.6, 10.12.3) OS. 2. Unable to reproduce issue in Firefox and Internet Explorer as the right click context menu does not show 'Open link in new tab' option.
,
Jul 4 2017
My CL is in PDFium (not Blink), which does not affect background color of tabs that are not PDFs. Reassigning back to you.
,
Jul 6 2017
,
Jul 6 2017
Yeah, this feels like the background from the first tab is rendered while waiting for a new CompositorFrame from the second tab's renderer. In this particular case (a tab that loads an email address, rather than a page with content), maybe the renderer doesn't submit one, even though it is supposed to. Provided that regression range is correct, and given the change log, I'd guess that it might be related to https://codereview.chromium.org/2802503002 by chrishtr@. Chris, what do you think?
,
Jul 11 2017
Yes, my commit technically caused this. However, mailto links are special external links, and do not actually spin up a corresponding Blink instance. I'm not so sure this is worth fixing. Leaving unassigned for now.
,
Jul 12
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 14
Update: ***Mass UI Triage*** Issue is still reproducible on Windows (7, 8, 10) and Linux (14.04 LTS) using latest canary #72.0.3609.3. Please refer the attached screen-shot. Thank You! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jmukthavaram@chromium.org
, Jul 4 2017Labels: hasbisect
Owner: npm@chromium.org
Status: Assigned (was: Unconfirmed)