4 ms·
Then there is someone nearly the same who cries foul when they aren’t told a new company owns the extension. What if Google bought it and was going to harvest t
by TheJoeMan 4y ago
Then there is someone nearly the same who cries foul when they aren’t told a new company owns the extension. What if Google bought it and was going to harvest that “ability to read and change website data” permission?
- Ajedi32 4y agoYeah, I dislike the intrusive nature of the notification, but I can't really think of a better way off the top of my head. The notification API could work in theory, but if you don't already have that permission it would be odd to request it just for a one-time message like this.
- ls15 4y agoIt should tell you before you install or update the extension, not randomly when they decide that now is the best time.
- andrewstuart2 4y agoI'm assuming that an extension update is precisely what triggered this behavior. It sounds like the extension had no need for alert functionality, and that this was a first occurrence, so I'd also assume they had to add code to trigger an alert rather than just blasting a brand new alert to users via written but previously-unused code.
- mh- 4y agoI'm fairly sure the Chrome Extension API doesn't have a way to implement "before self-updating, do this thing". This might have been their best/only option. The only other approach would be to notify them post-update.