Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-Bandcamp Domains Blocked #90

Open
sabjorn opened this issue Sep 23, 2021 · 4 comments
Open

Non-Bandcamp Domains Blocked #90

sabjorn opened this issue Sep 23, 2021 · 4 comments

Comments

@sabjorn
Copy link
Owner

sabjorn commented Sep 23, 2021

Bandcamp allows for custom domains and because the manifest for the extension is only wildcarded to "*.bandcamp.com", these don't work.

A user suggested adding the ability to choose custom domains BUT this still requires the manifest to wildcard to all domains. This could be a problem with the review process for publishing.

@emcniece
Copy link
Collaborator

emcniece commented Sep 23, 2021

Some extensions do operate on full wildcard: most adblockers, Tampermonkey, etc. It should be possible to get past review with a wildcard, but you're right in that the reviewer could request changes.

Something to consider will be the extension footprint when loading on other domains. Does the extension rely on certain elements (JSON blobs, particular IDs) or libraries (jQuery) being present in the DOM? When the extension initializes, does it load all of its bundled code into the runtime? Is there a way to structure JS functions and closures in a way that doesn't load or get parsed immediately, so that the extension can minimize its impact on pages where it isn't required?

Ensuring the extension plays nicely on all pages is responsible 👍

@sabjorn
Copy link
Owner Author

sabjorn commented Oct 2, 2021

@emcniece very good question. Currently the "main" of the application will at least skip code execution if certain components are not present on the page (sometimes it's a url matching, other times it's checking for an element on the page).

So, yeah, I think everything loads on runtime but execution is limited. We should investigate this next time we hang out.

@Sporradik
Copy link
Collaborator

Sporradik commented Sep 25, 2024

If it helps, you can make an optional_host_permission with a wildcard and then enable scripting as an optional permission in your manifest. Then you can request wildcard domain access as an optional setting or perhaps even white list individual domains that the user specifies.

This may still impact the review process, but I believe not as much as if it is a base level permission. Also it is less alarming to users as they will only be warned about that level of access when it contextually makes sense. Otherwise people may be skeptical to allow such blanket access initially.

@sabjorn
Copy link
Owner Author

sabjorn commented Sep 30, 2024

@Sporradik thank you for this info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants