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

Pausing Manifest V2 phase-out changes

groups.google.com

Post reply on HN
Print view View original

71–80 of 170 posts

Re: Pausing Manifest V2 phase-out changes

#71

Post by tssva »

gnicholas wrote: post #48
tssva wrote: post #45

Earlier quoted context omitted.

This isn't a new pause of the rollout. It is a message giving a general update on changes made to the APIs since the pause announced months ago began.

My reading is that this announcement indicates a new quasi-indefinite pause, beyond what was previously announced. They will probably still phase out v2, but every additional message about this pushes the timeline back further (even if it’s not explicitly mentioned). BTW, does anyone know how to subscribe to these Chrome updates? I’m kinda surprised not to get them via email, considering I manage multiple Chrome exte…

The December pause announcement stated it was until at least January 2024. This update still mentions a timeline of next year for v3. I find it hard to read as anything beyond the update of progress which was promised for March when the pause was announced in December.

Re: Pausing Manifest V2 phase-out changes

#72

Post by preinheimer »

People who want to release a new, cross browser, extension are left in a crappy position.

Chrome won’t accept a new manifest v2 extension. MV3 extensions have lots of problems in chrome, and are even worse supported everywhere else.

Google needs to reopen mv2 to new submissions until they’ve got things figured out, and the other browsers are on board.

Re: Pausing Manifest V2 phase-out changes

#73

Post by 20after4 »

capitainenemo wrote: post #64
sgtfrankieboy wrote: post #54

Earlier quoted context omitted.

Switched to Firefox for like 6-12 months, eventually moved back to Edge a couple of weeks ago. Had to open it constantly anyways. I couldn't get used to Firefox's DevTools and the JSON viewer in Firefox is bad compared to the JSON Formatter chrome extension.

Huh. I'm rather surprised you're comparing the out of the box firefox json formatting (rather good compared to chrome's non-existent formatter) to an extension. Are there no JSON formatting extensions for firefox?

I used an extension a while ago, however, it became unnecessary once the built in json view was implemented. Not sure if it's still around or whether it offers any advantage over the built in feature.

Re: Pausing Manifest V2 phase-out changes

#74

Post by darreninthenet »

judge2020 wrote: post #51
kej wrote: post #46

Earlier quoted context omitted.

You can just do this anyway, you know. Firefox is pretty great these days.

Especially on macs

I found it's lack of support for native functionality in MacOS too irritating (eg doesn't support system wide autocomplete - so my @@ shortcut that puts my email address in doesn't work in FF - I know I could put it in again in FF but it's annoying it just doesn't work) so I went back to Chrome in the end.

I was using Edge for a while but the absolute car crash their UI has become - and can't be configured - sent me running screaming for the hills.

Edit - and don't get me started on the massive slowdowns once I have more than a handful of tabs open.

Re: Pausing Manifest V2 phase-out changes

#75

Post by cpeterso »

bobse wrote: post #43

Microsoft Teams is still broken on Firefox? Linux app was also killed by Microsoft liars.

Mozilla had been working with Microsoft to resolve Teams compatibility issues.

Teams users using teams.microsoft.com (primarily Business and Enterprise customers on a paid plan, but also some free/personal legacy accounts) should be able to use Teams without issues now.

However, there is a second Microsoft Teams instance running on teams.live.com. Most Personal/Consumer/Free users of Teams are on that version, and there, Teams is currently showing a "browser unsupported" banner.

https://github.com/webcompat/web-bugs/issues/25070#issuecomm...

Re: Pausing Manifest V2 phase-out changes

#76

Post by hsbauauvhabzb »

xchkr1337 wrote: post #56
kej wrote: post #46

Earlier quoted context omitted.

You can just do this anyway, you know. Firefox is pretty great these days.

I wish Mozilla focused more on Linux support. I tried switching to Firefox multiple times, and in day-to-day use I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches etc. Problems like this never happen when I'm using Firefox on Windows, and honestly the state of Firefox on Linux is kind of surprising since it's the most commonly recommended and preinstalled brows…

I can’t report any of those issues, my biggest gripe is Ubuntu forcing a snap package on to me

Re: Pausing Manifest V2 phase-out changes

#77

Post by akomtu »

charcircuit wrote: post #58
blibble wrote: post #36

Earlier quoted context omitted.

> One thing that I'm sure about V3 is that it isn't well thought-out at all. that's because it's been invented for the sole purpose of making "breaking effective ad-blocking" look legitimate

From what I've seen the main purpose is to increase secruity, privacy, and performance of the extension ecosystem. I have seen no sign of mv3 being for breaking ad blocking. MV3 and other parts of chromium have added features that help ad blockers.

That's lie pushed by Google. MV3 removes the ability to block requests, but keeps the ability to observe requests. Great for ads-related spying.

Re: Pausing Manifest V2 phase-out changes

#78

Post by kivle »

loxias wrote: post #57
kivle wrote: post #52

Earlier quoted context omitted.

Using 2-3x as much battery as all other browsers on my Macbook is the dealbreaker for me.. I want to use the same browser on all systems when I move..

IME Firefox (esp with the right extensions, like autosuspend tabs) is very light on system resources. A bit more so than chrome. I run only Linux though. All the "websites that should be a program" (Netflix, Hulu, Slack, Amazon Video) now run great in FF, without my computer overheating. (though some of them might be on the chopping block if they don't quit blocking me from seeing HD content) I hear Apple does some s…

Honestly I do not think Apple does some special magic on Mac OS for Safari. I settled on Vivaldi (a chromium based browser with built-in ad blocking developed by former Opera devs). It gives battery life not much worse than Safari to be honest. Safari is very nice and snappy on a mac, but the extension support is extremely limited.

Re: Pausing Manifest V2 phase-out changes

#79

Post by hsbauauvhabzb »

John23832 wrote: post #40

As someone who has made an extension for an actual product, this whole rollout/situation has been an absolute shitshow. This is, what, the third pause of the rollout? Google stopped accepting V2 extensions sometime last year, pushing V3 but totally ignoring MANY of the current use cases of extensions that V3 just doesn't work for. Firebase auth, a Google freaking product, doesn't work in V3 (you can make it work with…

A few months back a HN user suggested it may be wise to continually delay an unpopular change, im no PR expert but I thought that was an interesting perspective.

Re: Pausing Manifest V2 phase-out changes

#80

Post by i_love_cookies »

20after4 wrote: post #60
xchkr1337 wrote: post #56

Earlier quoted context omitted.

I wish Mozilla focused more on Linux support. I tried switching to Firefox multiple times, and in day-to-day use I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches etc. Problems like this never happen when I'm using Firefox on Windows, and honestly the state of Firefox on Linux is kind of surprising since it's the most commonly recommended and preinstalled brows…

I'm using Firefox on Linux¹ and I have experienced none of those problems. Although I'm not particularly happy with the direction that Mozilla has been headed, Firefox is certainly a vast improvement over Chrome or even Chromium. 1. Latest version of Firefox (not ESR), Latest Debian, both Intel & AMD graphics. I can't speak for NVIDIA graphics on Linux as I gave up on NVIDIA a few years ago.

It depends on how Firefox was installed, snap and flatpaks are becoming the default for firefox on a few distros every variant of each that I've tried has those issues

I usually have to download the developer edition from the website and setup a desktop entry for decent performance

Post reply on HN