@simon Wow. The rabbit hole is deeper. In Debian Chromium...

@simon Wow. The rabbit hole is deeper.

In Debian Chromium
- the new tab page with google can access chrome.runtime
- the new tab page with something else can't
- a tab with www.google.com can't

So there is clearly a special case for www.google.com somewhere.

Like 10 July at 18:36 | Wall-to-wall | Open on chaos.social

2 comments

waldi

@simon Let's open this as a documentation problem: https://issuetracker.google.com/issues/352345933

10 July at 18:47 | Open on chaos.social

waldi

@simon Okay, one reason is: that extension is not enabled in the Debian build. And it seems the chrome.runtime API is made available if any extension allows the current page to communicate. Just no idea yet, why the new tab page can do that sometimes.

10 July at 19:56 | Open on chaos.social

Go Up