Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome phasing out Manifest v2 support from Jan 2022

developer.chrome.com

Post reply on HN
Print view View original

21–30 of 34 posts

Re: Chrome phasing out Manifest v2 support from Jan 2022

#21

Post by guilhas »

asddubs wrote: post #12

Is there an easy way to run two profiles of firefox simultaneously? As it stands I use FF with a bunch of extensions that limit what it can do (uMatrix, cookie zappers, etc.) and then occasionally when I just want to quickly view something I open it in chromium (and I also use it for youtube). But if they're going to cripple ad blockers (among other things) I'd rather just do it all in firefox

You can run:

firefox -no-remote -profile ./ff

It will create the folder and a new Firefox profile there

Optionally you can download Firefox portable

Re: Chrome phasing out Manifest v2 support from Jan 2022

#22

Post by asddubs »

magicalhippo wrote: post #14
asddubs wrote: post #12

Is there an easy way to run two profiles of firefox simultaneously? As it stands I use FF with a bunch of extensions that limit what it can do (uMatrix, cookie zappers, etc.) and then occasionally when I just want to quickly view something I open it in chromium (and I also use it for youtube). But if they're going to cripple ad blockers (among other things) I'd rather just do it all in firefox

> Is there an easy way to run two profiles of firefox simultaneously? Start one of them with firefox.exe -p profile_name -no-remote I do this to run the beta and the stable version at the same time. More details here: https://support.mozilla.org/en-US/kb/profile-manager-create-...

thank you

Re: Chrome phasing out Manifest v2 support from Jan 2022

#23

Post by adomasven »

rektide wrote: post #7

Some absolutely cavalier bombastic bullshit that Google is going to finally send a messenger to the WebExtensions working group like a week or two before they shut off capable MV2[1], having never ever replied to any of the massive massive outpourings of dismay, sadness, & hatred. Just dogshit apocalypically bad mishandling, complete & utter trashfire stewardship. This is the most trust-breaking saddening enraging th…

Citing something from one of the OPs posts on github

> The web & user agency doesn't deserve to be hurt like that & such aggression should be actively strenously heavily resisted.

I think a lot of people (who are mostly developers, since this hasn't affected the end users yet) are watching the situation with a similar feeling. I've myself considered just straight up writing a new browser, but that is obviously an insurmountable task for a single person in the current age of the web. I hate having to do politics, but I think it's time to do politics. Someone (like OP) needs to organize, write a petition, run a public poll, propose an actual way forward, more widely publicize the corrupt nature of what Google is doing with MV3 and get an actual voice out there. I bet lots of people would be willing to contribute financially or otherwise.

Re: Chrome phasing out Manifest v2 support from Jan 2022

#24

Post by 8K832d7tNmiQ »

skc wrote: post #16

It's been puzzling to me just how slow developers have been to adopt v3. Even right now if you look at a brand new extension created yesterday, or read a chrome extension tutorial from last week...they completely ignore the new manifest requirements. And Google has been clear for a very long time that v2 was being phased out, so what gives? Laziness? Inertia?

either there's a lack of proper documentation, developers unaware of the newer version, lack of interest within the company, or all of those.

Re: Chrome phasing out Manifest v2 support from Jan 2022

#25

Post by unionpivo »

asddubs wrote: post #12

Is there an easy way to run two profiles of firefox simultaneously? As it stands I use FF with a bunch of extensions that limit what it can do (uMatrix, cookie zappers, etc.) and then occasionally when I just want to quickly view something I open it in chromium (and I also use it for youtube). But if they're going to cripple ad blockers (among other things) I'd rather just do it all in firefox

Best solution i found is to have normal firefox + Firefox Developer Edition

They use separated profiles (you could sync them to same if you wanted)

https://www.mozilla.org/en-US/firefox/developer/

Re: Chrome phasing out Manifest v2 support from Jan 2022

#26

Post by unionpivo »

rektide wrote: post #7

Some absolutely cavalier bombastic bullshit that Google is going to finally send a messenger to the WebExtensions working group like a week or two before they shut off capable MV2[1], having never ever replied to any of the massive massive outpourings of dismay, sadness, & hatred. Just dogshit apocalypically bad mishandling, complete & utter trashfire stewardship. This is the most trust-breaking saddening enraging th…

You have put into words, what I have been feeling.

Thank you

Re: Chrome phasing out Manifest v2 support from Jan 2022

#27

Post by thrower123 »

skc wrote: post #16

It's been puzzling to me just how slow developers have been to adopt v3. Even right now if you look at a brand new extension created yesterday, or read a chrome extension tutorial from last week...they completely ignore the new manifest requirements. And Google has been clear for a very long time that v2 was being phased out, so what gives? Laziness? Inertia?

I dream of a day when enough people stop chasing the new shiny thing, and development churn returns to a more sensible and sustainable pace.

Re: Chrome phasing out Manifest v2 support from Jan 2022

#28

Post by lucasyvas »

Glench wrote: post #20

Yeah this is a very awkward release, and not just because MV3 cripples the most important extensions (adblockers). Firefox also hasn't released MV3 support yet so extensions that are cross-browser can't be MV3, which will be really annoying when Chrome no longer accepts MV2 extensions. I ran into this just yesterday when I tried to release an extension that removes those stupid fixed banners that take up vertical scr…

Has Mozilla committed to supporting both versions into the future? Or do they intend to bend over?

Re: Chrome phasing out Manifest v2 support from Jan 2022

#29

Post by Glench »

lucasyvas wrote: post #28
Glench wrote: post #20

Yeah this is a very awkward release, and not just because MV3 cripples the most important extensions (adblockers). Firefox also hasn't released MV3 support yet so extensions that are cross-browser can't be MV3, which will be really annoying when Chrome no longer accepts MV2 extensions. I ran into this just yesterday when I tried to release an extension that removes those stupid fixed banners that take up vertical scr…

Has Mozilla committed to supporting both versions into the future? Or do they intend to bend over?

You can read the details here: https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...

TLDR: They're officially going to support MV3 but also not going to deprecate the network blocking APIs that Google is.

Re: Chrome phasing out Manifest v2 support from Jan 2022

#30

Post by Glench »

paulryanrogers wrote: post #6

Fear of this delayed my starting work on Browser Routr; let's me intercept clicks to send some sites to other browser. In hindsight I don't think I need Manifest v2 on Chrome. Though I do need it on Firefox because of some quirks in their navigation API. And it's possible the nav APIs in Chrome or other Chromium browsers may need it someday, so still a loss IMO.

Seems like a useful extension! How do you get different browsers to open with an extension?
Post reply on HN