Breaking changes of manifest v3(version 1.17.0)

[brookhong]

Hi All,

On September 16, 2024, 1.17.0 was released(only for Chrome now, from branch mv3) to address manifest v3 upgrade, otherwise the extension would be taken down from chrome web store.

For now, please turn on Developer mode from chrome://extensions/ after you installed/upgraded to 1.17.0, due to following reason

The 'userScripts' API is only available for users in developer mode.

See offical docs from Google.

Then restart your browser, most features should work. And here are some known issues

• api.vmapkey is missing.
• api.Hints.setCharacter is missing.
• settings.blocklistPattern is not working.
• chrome.storage is not allowed in setting snippets.

[lost22git]

please turn on Developer mode

It's working fine for me, thanks.

[lcaturelli]

Enabling developer mode, manages to load and save settings from URL successfully.

However, settings fails to apply (extension works with the default configuration). In console it shows the following errors:

I confirm that, if enabled/disable "developer options", it is necessary to restart the Browser to apply the change.

Vivaldi 6.9.3447.37 (Stable channel) (32 bits).

I am available if I can help with tests.

[joshuali925]

seems api.Normal is also missing

[nekowasabi]

Same error by saving advanced mode setting.

[kings2u]

Thank you for addressing this so quickly. FYI, this line in my config also causes an error:

chrome.storage.local.set({"noPdfViewer": 1})

[daanzu]

[SurfingKeys] Error found in settings: TypeError: Hints.setNumeric is not a function

[agguser]

Uncaught TypeError: api.Front.showBanner is not a function

[voidpainter]

settings.prevLinkRegex, settings.nextLinkRegex not working

[wthueb]

For those of you with the know how, checkout commit f821819 (1.16.1) and build it from source yourself, and load the unpacked extension. The APIs still work, the new update just had to remove them to not get removed from the Chrome Web Store.

This won't work forever as Manifest v2 will eventually be unsupported entirely, but for now it allows Surfingkeys to be usable on Chrome for me.

[Kiraalla]

When will it be updated to [version 1.17.1]

[desgua]

Can someone guide me on how to build from source?
I have done (in Linux terminal):

git clone https://github.com/brookhong/Surfingkeys.git
cd Surfingkeys
git checkout f82181963

Then I go to chrome://extensions/ but when I try to load unpacked I get an error "Failed to load extension
File
~/Downloads/surfingkeys/Surfingkeys/src
Error
Required value 'version' is missing or invalid. It must be between 1-4 dot-separated integers each between 0 and 65536"

[psych3r]

@desgua You have to build the extension first.
Run the following commands in the extension directory:

npm install
browser=chrome npm run build:prod

Then load unpacked dist/production/chrome

[desgua]

@psych3r Thank you so much! <3

[snowman]

For those of you with the know how, checkout commit f821819 (1.16.1)

why there is not git tag for this...

[clarkwang]

As a workaround for settings.blocklistPattern, I use api.unmapAllExcept([], url_pattern) to unmap all keybindings for specific sites. For example:

api.unmapAllExcept([], /^https:\/\/(calendar|contacts|docs|drive|keep).google.com/);

[lpanebr]

As a workaround for settings.blocklistPattern, I use api.unmapAllExcept([], url_pattern) to unmap all keybindings for specific sites. For example:

api.unmapAllExcept([], /^https:\/\/(calendar|contacts|docs|drive|keep).google.com/);

unfortunately this workaround is not working for me (developer mode enabled).

This is so sad...

[brookhong]

1.17.1 has been released, above mentioned issue should have been resolved.

[lpanebr]

This is very unfortunate. I've tried other extension but it doesn't cut it. I miss surfing the web.

…

Message ID: ***@***.***>

[brookhong]

Closing this since all known issues from MV3 upgrade have been fixed now.

[agguser]

Uncaught TypeError: api.insertJS is not a function

[rosshadden]

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'addListener')

    chrome.runtime.onMessage.addListener((function(e, t, n) {
        i[e.subject] && i[e.subject](e, t, n)
    }

I even get this with an empty config. On version 1.17.3.

Edit: This seems to be fixed as of today :).