@simon Hmm, my Chromium 126 does not even allow me...

@simon Hmm, my Chromium 126 does not even allow me to access the `chrome.runtime` API from any page. It is also mentioned that this API is for extensions and content scripts, aka not for plain pages.

Like 10 July at 14:40 | Wall-to-wall | Open on chaos.social

5 comments

Simon Willison

@waldi not even on a www.google.com page? I can't access chrome.runtime on other sites but it works for me on Google pages

10 July at 15:14 | Open on fedi.simonwillison.net

waldi

@simon Nope. Maybe a change to the commercial Chrome.

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

waldi

@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.

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

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