13

Steps to reproduce:

  1. Go to the Chrome Web Store
  2. If offered, use the new UI experience [figure 1] (If not offered, then you'll need to wait until you're in a rollout bucket.)
  3. Go to any extension page and try to install an extension
  4. Observe that the "Add to Chrome" button is disabled and a banner exists asking to switch to Chrome. [Figure 2]

Expected behavior:

To be able to install extensions.

Extra info:

It appears as if this is due to a new location move where the internal Google script for various APIs they have is being called. [Figure 3] It is now within an iframe on an origin that is triggering some stepped up Webkit blocking. Oddly though, I can't seem to find any way to alleviate the permissions to let this to work.

Orion, OS version; hardware type:

Version 0.99.125.1-rc (WebKit 616.1.22)
MacBook Pro (macOS Ventura 13.5.1 build 22G90)

Image/Video:

Figure 1:
new chrome web store experience trigger

Figure 2:
disabled add extension button

Figure 3:
console error on web store extension page

    I can confirm it doesn't work, even with user agent set to Chrome and compatibility mode enabled. The old store still works as expected. Version 0.99.125.1-rc (WebKit 616.1.22)

      Same problem, new Chrome Store won't install extensions！
      Hopefully this will be fixed!

        2 months later
        22 days later
        13 days later
        6 days later

        This is an issue on iPadOS too. Tried a reinstall but issue persists.

        8 days later
        No one is typing