--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/36c73692-5adf-4cb7-9b6e-cecfad4e41den%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CADq%3D7qv1uucav2_J0Sd13oSiT01Qo72afVKX6VYFyvuxMOeOtg%40mail.gmail.com.
If a user enables developer mode, is that enabled for all extensions or only ones the user trusts?
May I ask what is the motivation for having two user-authorization mechanisms (the userScripts permission and the developer mode checkbox) behind the userScripts API? Why is the userScripts permission not enough authorization?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/8b8081b6-aed2-44fb-b0cf-3178b2af472bn%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAPAuxoDXvBaTeC0zTjSitQfgS1WA-B8jDR_xSTv%3DBneCBY7ESA%40mail.gmail.com.
I was just reacting to the message by "Pavel Aronovich" who claims "If the extension is installed by policy, then you do not need to require anything additional for userScripts to work."
TBH this communication is a complete mess up to now. We received an update on the google store policy on Saturday that the policy has changed to make the use of external code possible again (via debugger API and userscript API), but at this point, the UserScript API is completely unusable due to the requirement to have the developer mode active. This is not something that works with policies and this is not something that works reasonably well for end users.
As far as globs, I'm trying to resolve legacy userscripts. Some of the @include params target openly like `*groups*` so that the script runs on domains like groups.google.com but not others. I'm assuming since matches is required that I can match for google.com, then use includeGlobs to only match the `groups` URLs. Please correct me if I'm wrong, but my test scripts run on all the google.com URLs instead of the groups filter as I expect.
Are we expected to use chrome.alarms to poll every 30s until developer mode is enabled, then show the quick start guide?
How are you guys handling opening the quick start guide when the extension requires developer mode? Usually, we'd launch the quick start guide from chrome.runtime.onInstalled, but if the user doesn't have developer mode mode enabled when installing the extension, the quick start guide never opens.Are we expected to use chrome.alarms to poll every 30s until developer mode is enabled, then show the quick start guide?
> I know this is tricky and we're continuing to talk about the developer mode requirement internally :)
"tricky" is an understatement that has a very deceptive connotation as though it takes some kind of exceptional skill to master this super advanced feature. For something that has so many inherent problems as multiple developers pointed out a better description would be weird, awkward, wayward, counter-intuitive, confusing.
Enabling Developer mode is not possible in a corporate environment. This requirement is absurd.
On May 21, 2024, at 10:58 AM, Oliver Dunk <olive...@google.com> wrote: