Thanks for filing this. Somehow I was unable to repro the issue on the reported version: 60.0.3111.0 on Mac OS 10.12.4.

@reporter: Could you please review the attached screen-cast and confirm if anything being missed here.

Deleted: 727046.webm 4.0 MB

	727046.webm 4.0 MB View Download

Hmm that was strange, you are doing the same thing as me except that it works as expected for you. I got it on Linux too. Let me try again later today and update the issue, maybe the I did run on an earlier version.

Thank you for providing more feedback. Adding requester "ajha@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

Wait a minute, it says my "Chrome version: 60.0.3111.0  Channel: canary" but if you read the issue I tried Chrome 59 (also 59 on Ubuntu). Could it be then that it has been fixed between 59 and 60? Can you try in 59 as I reported?

I've downloaded latest beta 59 (Version 59.0.3071.82 (Official Build) beta (64-bit)) and it happens there but not for every try.

I can repro this on ToT Linux.

This looks very much like the fix to avoid white flashes during page navigation is picking up the wrong color in situations like this. Over to chrishtr@ to validate my theory.

The fix regressed a couple of times, which may explain why reproduction seems random.

Unable to reproduce this issue on Ubuntu 14.04 with chrome 61.0.3112.10, performed steps as mentioned in comment #0.

Didn't observe any change in background color while loading the url.

Attaching a screen-cast for reference.

poppap@ could you please look into it and let us know your observations.

Deleted: Issue 727046.mp4 4.8 MB

	Issue 727046.mp4 4.8 MB View Download

Hey! I've reported it on Chrome 59, could it be that it has been fixed then to 61? If you want to see the problem, please test on 59 :)

Do you want me to test on 61 on Ubuntu?

Thanks for the reply.

Able to reproduce the issue on Ubuntu 14.04 using chrome#59.0.3071.86 only on the first build after chrome installation as per the below steps.
1. Open Chrome 
2. Open Developer Tools
3. Clear Console & enter document.body.style.background = "#DE640D" & observed background color changed to orange
4. Next enter document.body.style.background = "#FFFFFF" & observed background color changed to white
5. Enter a URL https://en.wikipedia.org/wiki/Barack_Obama in the address bar of same page, observed orange screen for a while ( 1 sec)& immediately webpage displayed properly

Unable to reproduce the same issue for the next time on the same build on Linux Ubuntu ( new tab or new window)

Note: Unable to reproduce the issue on Mac & Windows 7 using 59.0.3071.86 & Canary-61.0.3122.0

We are unable to provide bisect from our end as this issue observed inconsistently .

poppap@, if possible could you please provide any other sample test/html file to reproduce the issue.

Hmm did you not see that pfeldman@chromium.org could reproduce on Linux (comment 8)? Check also comment 9. It's also reproducible on Mac Version 59.0.3071.86 (Official Build) (64-bit) now when 59 is stable. Try a couple of times and I hope you will see it.

I can reproduce at ToT with https://chromium.googlesource.com/chromium/src/+/94fdfaa5a34534601337ce1780eb8fe381f74c3b reverted.

It looks like the background color sent from cc to RenderWidgetHostView
as a parameter to the CompositorFrame is stale by one frame. Digging now
to find out why that is the case.

The delay by a frame is due to WebViewImpl setting the root background color
before running the lifecycle. I introduced this bug in
https://codereview.chromium.org/1526093006.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e76d87acc9a55f551ddab222b5f8f656eee63042

commit e76d87acc9a55f551ddab222b5f8f656eee63042
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Fri Jun 09 05:42:37 2017

Set the LayerTreeHost background color after updating the
DocumentLifecycle, not before.

This way any changes to the background during that update
will apply to the background passed to the LayerTreeHost.

Bug:  727046 
Change-Id: I5c2d080ffdbe52bb3d23a8bd99feb92eab1ade8a
Reviewed-on: https://chromium-review.googlesource.com/528543
Reviewed-by: Walter Korman <wkorman@chromium.org>
Commit-Queue: Chris harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#478210}
[modify] https://crrev.com/e76d87acc9a55f551ddab222b5f8f656eee63042/third_party/WebKit/Source/web/WebViewImpl.cpp
[modify] https://crrev.com/e76d87acc9a55f551ddab222b5f8f656eee63042/third_party/WebKit/Source/web/tests/WebFrameTest.cpp
[modify] https://crrev.com/e76d87acc9a55f551ddab222b5f8f656eee63042/third_party/WebKit/Source/web/tests/sim/SimCompositor.h

This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Can you please confirm if this fix is verified in canary or dev?

I verified it in Canary just now.

I tried on Ubuntu Google Chrome "61.0.3124.4 dev" and still got the flashing, but maybe isn't there yet?

IT's in Canary but not yet Dev.

Verified the fix on Mac 10.12.5 using Chrome dev version #61.0.3128.0 as per the comment #0.
Attaching screen cast for reference.
Observed that background color was first orange then white and then stayed white until first paint happened for the entered URL as expected.
Hence, the fix is working as expected. 
Adding the verified labels.

Thanks...!!

Deleted: 727046.mp4 3.4 MB

	727046.mp4 3.4 MB View Download

Ping - can I please merge this to M60?

Approving merge to M60. Known bug regression, and fix is well tested in canary. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/21058e1a3ab1a8931ceb689615302c0b8f6484e3

commit 21058e1a3ab1a8931ceb689615302c0b8f6484e3
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Fri Jun 16 20:48:41 2017

Set the LayerTreeHost background color after updating the DocumentLifecycle, not before.

This way any changes to the background during that update
will apply to the background passed to the LayerTreeHost.

TBR=chrishtr@chromium.org

(cherry picked from commit e76d87acc9a55f551ddab222b5f8f656eee63042)

Bug:  727046 
Change-Id: I5c2d080ffdbe52bb3d23a8bd99feb92eab1ade8a
Reviewed-on: https://chromium-review.googlesource.com/528543
Reviewed-by: Walter Korman <wkorman@chromium.org>
Commit-Queue: Chris harrelson <chrishtr@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#478210}
Reviewed-on: https://chromium-review.googlesource.com/538863
Reviewed-by: Chris harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/branch-heads/3112@{#367}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
[modify] https://crrev.com/21058e1a3ab1a8931ceb689615302c0b8f6484e3/third_party/WebKit/Source/web/WebViewImpl.cpp
[modify] https://crrev.com/21058e1a3ab1a8931ceb689615302c0b8f6484e3/third_party/WebKit/Source/web/tests/WebFrameTest.cpp
[modify] https://crrev.com/21058e1a3ab1a8931ceb689615302c0b8f6484e3/third_party/WebKit/Source/web/tests/sim/SimCompositor.h