4 ms·
> A good way to inform your users is to combine chrome.runtime.OnUpdateAvailable and chrome.tabs.create(<INSERT blog URL>) . This is terrible behaviour. I can
by paranoidrobot 3y ago
> A good way to inform your users is to combine chrome.runtime.OnUpdateAvailable and chrome.tabs.create(<INSERT blog URL>) .
This is terrible behaviour.
I can't express how much it frustrates me that every extension and every service thinks it's a great idea to launch new tabs or overlay the screen I'm trying to use with their self promotion about some new update or change they rolled out.
Unless there is something I have to know about immediately because there will be significant side effects (data loss, monetary, physical danger, that sort of thing) don't do it.
- lcmchris 3y agoI think I am convinced, my wording here definitely does not help ('good' -> 'possible'). For sure a new feature does not warranty intrusive browser behaviour. Will make some edits.
- wahnfrieden 3y agoI also dislike it but please blame/advocate for Chrome change rather than devs with zero good options. Google created and maintains these conditions.
- pcthrowaway 3y agoIt's pretty responsible for devs to at least let us know when they make changes. Complain about it all you want in software where the user controls the update schedule, but extension devs don't have any other way to alert users to changes.
- lapcat 3y agoThey could simply badge the extension icon.
- nazgulsenpai 3y agoI assume many hide their extension icons. I do agree with not popping up a new tab or whatever, though.
- bunga-bunga 3y agoNo, I really don’t care. I have hundreds of apps on my phone, most of which I use once every few months or even years. Imagine if they opened some random popup every time someone decided they made huge changes. Same goes for some extensions, which most likely don’t have (or shouldn’t have) fundamental changes that require immediate action. Don’t bug your users. Note: I’m a Web Extension developer too.