This issue reproducible on previous stable#59.0.3071.115 as well for Win7 64-bit.

termsrv@Thanks for the issue.

Unable to reproduce the issue on windows 7, Mac 10.12.6 using chrome version 60.0.3112.78 and canary 62.0.3171.0 with the below steps

1. Go to URL https://www.google.co.in/search?q=weather+10538 in a new tab
2. Not observed any raw javascript 

Please find the attached screen cast and confirm if anything missed here.
Request you please try the issue on clean profile without any extensions/flags and update the thread if the issue still persists.

Thanks,

Deleted: 749715.mp4 782 KB

	749715.mp4 782 KB View Download

Well I don't know what to tell you. I can reproduce it here in Windows 7 but it only happens for a split second. The way I'm opening the tab is middle-click on the item in bookmarks and then I click on the tab. 

I can also reproduce it in the current tab (in other words just left-click on the bookmarks item but it's much less likely to happen.

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

Unable to reproduce the issue on windows 7 suing chrome M60 #60.0.3112.78 , bookmarked the given url and middle-clicked on it and didn't observe any raw script.

@redirecting it to UI team , as the issue is inconsistent . Could someone from UI team . Please look into this.

Thanks!

Able to reproduce the issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome stable version #60.0.3112.90 and latest canary #62.0.3180.0.

This is a non-regression issue as it is observed from M45 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!

This is not related to V8. I suggest looping in the Blink folks (already done) and/or get in contact with the Google search team. Seems like text (JavaScript) is written to the document and rendered.

Able to capture a screen record on Mac / Chrome stable.
In this case, the text looks like a part of stylesheet inside <style> tag in view-source:https://www.google.co.jp/search?q=weather+10538 .
Not sure why this is displayed as text...

Deleted: crbug749715.mp4 1.3 MB

	crbug749715.mp4 1.3 MB View Download

I was told that "script { display: block; }" in the CSS will do this. (but there's probably a little bit more to it than that)

Adding Layout and CSS labels, hoping someone in the teams could help debugging this.

I think there's two page loads going on here. First it loads https://www.google.com/#q=weather+10538, which displays garbage, and then https://www.google.co.jp/search?q=weather+10538&cad=h which displays fine.

I can reproduce easily in M-62 in guest mode. I cannot reproduce in M-60.

css wise: i have shown the issue to the style team, no luck so far with any debugging help i'm sorry

removing blink>css component for clearer ownership

This looks like a loader issue where it doesn't process the redirect at the end of the script block but does stop loading the css which triggers a layout without any styling. It is somewhat tricky to debug.

Could someone from the loading team please help look into this in detail?

 Issue 771060  has been merged into this issue.

BTW this happens only if the following URL is used:

 https://www.google.com/#q=...

It does not happen if you use canonical search result URL:

 https://www.google.co.jp/search?q=...

The former redirects to the latter.

It doesn't repro in Chrome 63 (beta).

Bisection suggested that this was fixed by 6593874a60b5694724d6a226ab1b0dfca71052a5, but I'm not sure what was happening.

+treib@, do you have any insights here?

Huh, weird. What that CL does is avoid some unnecessary renderer forks for URLs related to the default search engine. Per comments 12 and 17, maybe it's related to the redirect from .com to .co.jp somehow, since only one of the two will be considered the default search engine? Still, no idea how this would trigger the weird rendering bug.

Thanks.

Let me close this as fixed in M63. Although we don't fully understand the root cause, we don't have bandwidth to investigate it further.

 Issue 793416  has been merged into this issue.