dotproto

15 ms·

31.
by dotproto 5y ago
Sure. If you're the only one using it, you can just run the extension locally as an unpacked extension. Check out the step-by-step getting started guide: https://developer.chrome.com/docs/extensions/mv3/g
32.
by dotproto 5y ago
Manifest V3 does not currently support user script managers, but we are planning to address that gap in the coming months.
33.
by dotproto 5y ago
Yes-ish? So the extension itself is basically a bundle of web resources like HTML, CSS, and JS files. Today, the only way an extension can ask Chrome to automatically inject a content script on a page is to declare what scripts should be in
34.
by dotproto 5y ago
For clarity, injecting a script that is not included with the extension is expressly disallowed by the Chrome Web Store Developer Program Policies. > Some common violations include: > > * Including a <script> tag that points
35.
by dotproto 5y ago
Original blog post author here. The short answer is that Manifest V3 does not currently support these extensions (or their broader use cases), but we want to support them and have some ideas that we plan to explore.
36.
by dotproto 5y ago
Original blog post author here. Some quick personal thoughts (i.e. I'm not speaking on behalf of Chrome here). > - Blocking webRequest to change CSP to authorize our overlay script to execute I can't exactly say I'm keen o
37.
by dotproto 5y ago
What changes are you most concerned about? How does Manifest V3 negatively impact your extensions? You may want to consider getting involved in the recently announced WebExtensions Community Group in order to discuss your concerns with the
38.
by dotproto 5y ago
> it just seems so trivial to me too build a small interpreted system that circumvents the "no dynamic JavaScript" rule While it's possible to build an interpreter in JS, doing so in an extension is an unambiguous violatio
39.
by dotproto 5y ago
> They already disallowed remote code loading in extensions with a Chrome Web Store policy update nearly two years ago. They didn't have to invent a new API full of breaking changes to do it. Blog post author here. This comment is i
40.
by dotproto 5y ago
"They already win on UX" As someone that has tried and failed to get some small personal sites running on AWS a couple times, I'm going to have to tag this snippet with [citation needed].
41.
by dotproto 6y ago
You're giving HN a bit too much credit.
42.
by dotproto 6y ago
The CWS developer program policy does not allow extensions to request unnecessary permissions. If an extension doesn't have a good reason to observe network requests in MV3, it will/should be rejected. So yes, it's technicall
43.
by dotproto 6y ago
Correct, apps are depreciated and you can still upload new extensions.
44.
by dotproto 6y ago
This white paper may help https://support.google.com/chrome/a/answer/9296680?hl=en At some point I want to put together a simple Node.js server and ExtensionSettings policy to demo a basic working setup, but
45.
by dotproto 6y ago
You may be able to reach out to the Chrome Enterprise Browser Support team for assistance. https://support.google.com/chrome/a/answer/4594885?hl=en
46.
by dotproto 6y ago
Self-hosting is def an option. Check out "Managing Extensions in Your Enterprise" https://support.google.com/chrome/a/answer/9296680?hl=en . That's probably the single best resource for hosting
47.
by dotproto 6y ago
What's your extension ID?
48.
by dotproto 7y ago
Can't speak for other Chromies, but what's crossed my radar has been direct outreach from developers and bug reports.