News for hackers. Stuff that matters.

A comment on Manifest v3 in Firefox: Recap and Next Steps. Parent comment

Re:Manifest v3 in Firefox: Recap and Next Steps by mook on Wednesday May 18, 2022 @11:27PM (#31430333)
> But it wasnt a standard, other than that it was by far the highest potential most capable most interesting user-agency extension on the planet by a good measure.

While the Chrome extension API was certainly the most wide-reaching at the time, it wasn't the most capable. I used to have a Firefox extension that made Win32 API calls. Mozilla ended up deciding it wasn't sustainable, I guess?

[ Parent | on HN ]
Re:Manifest v3 in Firefox: Recap and Next Steps by sroussey on Thursday May 19, 2022 @02:14AM (#31431308)
The extension API for Firefox was simply the entire internal api of the browser. Making it work cross process (everything was single process) was a huge pain and things were going to break depending on how you used the APIs. And the security considerations of accessing every api was a big issue.

On the other hand, Firebug could not have been created without it…

[ Parent | on HN ]
Re:Manifest v3 in Firefox: Recap and Next Steps by rektide on Thursday May 19, 2022 @12:23AM (#31430740)
I very very very rarely try to declare someone's feature to be an anti-feature, but as a Linux user: the feature you proclaim is- distinctly & clearly- a huge antifeature I want kept far away from the web & it's extensions. What is a feature to you is a huge will not run anywhere else to me.
[ Parent | on HN ]