News for hackers. Stuff that matters.
Re:Firefox 115 can silently remotely disable my extension on... by indymike on Wednesday July 05, 2023 @12:55PM (#36603221)
The ability to prevent an extension from accessing specific sites is an improvement as long as the user can control it and it is not used for centralized access control.

The reason this feature is there is that many extensions play poorly with or should not have access at all to specific sites. For example, Grammarly has no business accessing a corporate billing system and IT might want to disable access. In other cases an extension slows a site massively and a user might want to say, "not that site" to an extension. This could be the start of a big end-user improvement, especially if it can be managed by users and installers.

Re:Firefox 115 can silently remotely disable my extension on... by ilyt on Wednesday July 05, 2023 @03:22PM (#36605728)
This as a feature attached to their containers would be pretty spiffy tbh. But as you said, if it was entirely user-controlled.
Re:Firefox 115 can silently remotely disable my extension on... by t00 on Wednesday July 05, 2023 @04:39PM (#36606778)
If that was the case, the feature should have been moved to site settings and labelled "Disable extensions on this site" or even better "Allow only specific extensions to run on this site".