News for hackers. Stuff that matters.
Re:Introducing chrome.scripting by tooker on Tuesday June 08, 2021 @07:50PM (#27442573)
V3 is a cancer. As a full time extension developer I am dreading the notion of chrome successfully deprecating V2. Hopefully developers can rise up against V3 before it's too late.
Re:Introducing chrome.scripting by dotproto on Wednesday June 09, 2021 @08:49PM (#27455420)
What changes are you most concerned about? How does Manifest V3 negatively impact your extensions?

You may want to consider getting involved in the recently announced WebExtensions Community Group in order to discuss your concerns with the future of browser extensions with browser vendors and other extension developers.

http://w3c.org/community/webextensions https://github.com/w3c/webextensions

Re:Introducing chrome.scripting by edoceo on Tuesday June 08, 2021 @08:33PM (#27442860)
What action can we take? Switching browsers is hardly going to make G blink.

Edit: I want add, recently built my own Firefox - pulled out all the Pocket shit and tweaked the UI a bit "my way". Was actually not that hard. I'd love to see 20 forks of Firefox trying different things. Also, anyone know what happened to Librefox?

Re:Introducing chrome.scripting by dannyw on Wednesday June 09, 2021 @05:53AM (#27446114)
Get enough attention from the EU, to get them to determine that on balance, Manifest v3 is designed to cripple ad blockers and abuse Google's monopoly on web browsers to benefit their monopoly on search advertising.
Re:Introducing chrome.scripting by smolyeet on Tuesday June 08, 2021 @08:52PM (#27442972)
Until Firefox us taken seriously by tech companies not google , it's inevitable. I've yet to encounter a website that doesn't work on chrome , but FF is a gamble between it not being supported or prevent ad tracking breaks it. Can't use teams in web despite it running a bit better than desktop , can't use most of my apple websites for work, least not without some extension so it's really just frustrating.

Honestly if chrome introduced bottom url bar and extensions without limitations... I'd switch back. I didn't switch for privacy but because chrome mobile is is clunky as a web app and I use my phone a lot during the day.

Re:Introducing chrome.scripting by breakingcups on Wednesday June 09, 2021 @05:04AM (#27445801)
I can count the number of times a website has not worked for me in Firefox the past 5 years on one hand.

Now contrast that with the number of extensions Chrome would break for me with this update. It's a bigger number. Luckily I'm already on FF.

Re:Introducing chrome.scripting by Lammy on Tuesday June 08, 2021 @08:46PM (#27442940)
That seems doomed to eventual irrelevance since web standards are now constantly-moving goalposts also authored by companies like Google.
Re:Introducing chrome.scripting by d3nj4l on Tuesday June 08, 2021 @11:12PM (#27443824)
This is my place to plug once again that Slack still doesn't support calls on Firefox, over four years since they were launched.
Re:Introducing chrome.scripting by vorpalhex on Wednesday June 09, 2021 @12:08AM (#27444126)
Users moved to Chrome and Firefox in part because of extensions. If users start getting notifications that their favorite extensions are no longer available on Chrome and they'll need to move to something else.. they're likely to follow.
Re:Introducing chrome.scripting by pmontra on Wednesday June 09, 2021 @12:55AM (#27444345)
Do you have a blog post about your build procedure?
Re:Introducing chrome.scripting by edoceo on Wednesday June 09, 2021 @01:20AM (#27444477)
No. I started here https://davidwalsh.name/how-to-build-firefox - it mostly "just worked". I'm on Gentoo so I already had all the build-deps (oh, I had to enable some PulseAudio crap tho)