Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome.userScripts API requires developer mode

developer.chrome.com

Post reply on HN
Print view View original

21–26 of 26 posts

Re: Chrome.userScripts API requires developer mode

#21

Post by tzs »

devsda wrote: post #17

The requirement is not without side-effects. From the chrome developer group[1] > The devmode switch also enables other features e.g. chrome.declarativeNetRequest.onRuleMatchedDebug which may severely reduce the performance of the content blocking extensions, depending on how it's used. Unless they are happy with degraded performance or needing to switch to developer mode often, users may have to chose between ad-blo…

> Unless they are happy with degraded performance or needing to switch to developer mode often, users may have to chose between ad-blocking and custom scripts.

Just going by the name, chrome.declarativeNetRequest.onRuleMatchedDebug, I'd expect that to be something that has to explicitly be used. Enabling developer mode would make it available which they say might reduce the performance "depending on how it's used", but would a production release of an ad-blocker extension be using it?

Re: Chrome.userScripts API requires developer mode

#22

Post by devsda »

devsda wrote: post #17

The requirement is not without side-effects. From the chrome developer group[1] > The devmode switch also enables other features e.g. chrome.declarativeNetRequest.onRuleMatchedDebug which may severely reduce the performance of the content blocking extensions, depending on how it's used. Unless they are happy with degraded performance or needing to switch to developer mode often, users may have to chose between ad-blo…

I'm unable to edit. So quick update:

As per [1], the chrome.declarativeNetRequest.onRuleMatchedDebug is available only for unpacked extensions i.e. local extensions with a specific permission. So, I'm not sure under what context there will be a performance impact.

Anyone more familiar with internals of chrome and/or extension development in general can clarify if there are any downsides to enabling dev mode permanently.

[1] https://developer.chrome.com/docs/extensions/reference/api/d...

Re: Chrome.userScripts API requires developer mode

#23

Post by lapcat »

devsda wrote: post #22
devsda wrote: post #17

The requirement is not without side-effects. From the chrome developer group[1] > The devmode switch also enables other features e.g. chrome.declarativeNetRequest.onRuleMatchedDebug which may severely reduce the performance of the content blocking extensions, depending on how it's used. Unless they are happy with degraded performance or needing to switch to developer mode often, users may have to chose between ad-blo…

I'm unable to edit. So quick update: As per [1], the chrome.declarativeNetRequest.onRuleMatchedDebug is available only for unpacked extensions i.e. local extensions with a specific permission. So, I'm not sure under what context there will be a performance impact. Anyone more familiar with internals of chrome and/or extension development in general can clarify if there are any downsides to enabling dev mode permanent…

A lot of people run with developer mode enabled permanently, especially extension developers, both professional and amateur.

I've seen no downsides myself.

Re: Chrome.userScripts API requires developer mode

#24

Post by gentleman11 »

mkl wrote: post #4

Currently I maintain a user script for myself and about 10 much-less-technical colleagues, which they install with Violent Monkey. With this change the ones who use Chrome will need to enable extension developer mode. Are there consequences to that, or is it just an extra step?

Why not just use Firefox?

Re: Chrome.userScripts API requires developer mode

#25

Post by haburka »

I have no clue why people are so shocked about this. Being able to run arbitrary code makes extensions nearly impossible to audit. There are so many malicious extensions out there, surely there has to be some checks on them. How else would the chrome extension store be able to prevent apps like Honey from harvesting all of your personal data?

Also, users can check one box in chrome settings in order to go around this. It’s a bit too easy to bypass IMO.

Post reply on HN