News for hackers. Stuff that matters.
Re:Manifest v3 Update by nonbirithm on Thursday May 27, 2021 @03:44PM (#27307324)
> extension makers will only consider porting to Firefox if it's as little effort as possible. Hence they need to support the same API's

At least the last time I developed a browser extension, this was not the case. I found that what was considered the WebExtension API was not 100% portable across browsers, and I had to rewrite parts of my code between Chrome and Firefox because Chrome had many extra APIs that Firefox lacked.

Re:Manifest v3 Update by Yoric on Thursday May 27, 2021 @04:00PM (#27307514)
If you compare with attempting to share code between XUL addons and Chrome extensions, you'll notice that things have gotten muuuuuuuuch simpler, though.
Re:Manifest v3 Update by Vinnl on Friday May 28, 2021 @06:51AM (#27313845)
"As little effort as possible" does not mean that it should be perfectly identical - sometimes that's just not an option. They're striving to be as close as possible though, and this is part of that.
Re:Manifest v3 Update by nextaccountic on Thursday May 27, 2021 @10:58PM (#27311263)
Isn't there any framework for abstracting away the differences between the two browsers? With polyfills or whatever.
Re:Manifest v3 Update by Vinnl on Friday May 28, 2021 @06:52AM (#27313849)