Most Visited iframe sends postMessages to wrong origin |
|||||||||
Issue description
Chrome: 64.0.3248.0 (Official Build) canary (64-bit)
OS: macOS 10.12.6
84 [92509:775:1025/131143.023979:ERROR:CONSOLE(168)] "Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://cs.chromium.org') does not match the recipient window's origin ('https://www.google.com').", source: chrome-search://most-visited/single.js (168)
85 [92509:775:1025/131647.817604:ERROR:CONSOLE(168)] "Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://cs.corp.google.com') does not mat ch the recipient window's origin ('https://www.google.com').", source: chrome-search://most-visited/single.js (168)
86 [92509:775:1025/135835.767422:ERROR:CONSOLE(168)] "Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://docs.google.com') does not match the recipient window's origin ('https://www.google.com').", source: chrome-search://most-visited/single.js (168)
,
Oct 26 2017
,
Oct 30 2017
Hm, so the most visited iframe is trying to send its 'loaded' postMessage to the wrong target origin. The target origin is determined in IframeSource::GetOrigin (https://cs.chromium.org/chromium/src/chrome/browser/search/iframe_source.cc?rcl=f5e1394c0eb5c11a773ef12796e9b111c36beb20&l=53), which should prooobably use NavigationController::GetLastCommittedEntry rather than GetVisibleEntry. But that code hasn't been touched in ages. Possibly related to bug 631937 , or to the recent --site-per-process trial on Canary? (Both of which might have changed timing/order of events in the vicinity.) However, I couldn't immediately reproduce. Any hints on repro steps? Were you just opening new tabs, or going to chrome://newtab in an existing tab, or something else entirely?
,
Oct 30 2017
I launched Chrome Canary with --enable-logging --v=1, and just ran it for ~1 day. I have a work account, chromium account, and personal account. Sorry, don't have more specific repro steps.
,
Oct 30 2017
,
Nov 28 2017
,
Jan 11 2018
,
Jan 12 2018
,
Jan 15 2018
,
Jan 16
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
,
Jan 18
(4 days ago)
Closing this issue as I am unable to reproduce. Please reopen if the issue occurs again! |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by fs...@chromium.org
, Oct 26 2017Components: UI>Browser>NewTabPage
Owner: ----
Status: Untriaged (was: Assigned)