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

Proxy Chrome extensions are not going to be usable in MV3

bugs.chromium.org

Post reply on HN
Print view View original

201–210 of 215 posts

Re: Proxy Chrome extensions are not going to be usable in MV3

#201

Post by HellsMaddy »

dotproto wrote: post #193
HellsMaddy wrote: post #125

Manifest V2 deprecation is likely going to break extensions that inject userscripts, like Tampermonkey [0] and SurfingKeys [1]. The Chrome team has been rather unhelpful. They've promised to add support for power-user tools like these in MV3: dotproto from the Chrome team commented on May 27 [2]: > @mon-jai, the short answer is no, I don't have any updates to share. That said, I'll reaffirm that we plan to support us…

Hey, I'm that Simeon/dotproto guy! We discussed Chromium's current plan to support user scripts managers in Manifest V3 during our WebExtensions Community Group (WECG) session at TPAC[1] last week. The notes for that meeting haven't been merged yet, but there's an open PR[2] and when they are they will live here[3]. In short, the current plan in Chromium is to require end users and extension authors to opt into execu…

I appreciate you sharing these resources. I would also like to apologize if my original comment was unfairly critical of the Chrome/Chromium Team. I understand MV2->MV3 is a complex and challenging endeavor. I just hope nobody gets left behind!

Re: Proxy Chrome extensions are not going to be usable in MV3

#202

Post by int_19h »

scoopertrooper wrote: post #150

Looks like we caught someone's attention: > I'm temporarily restricting comments to keep comments from turning into +1s while this is trending on Hacker News. If you have additional thoughts that you'd like to share with the Chromium team regarding this issue, please return in a few days to leave a comment (and apologies for the inconvenience). > As a Chromium contributor that shares information about our progress on…

What's really maddening is that it's the first comment from Google on that issue for over a year, despite numerous pleas of extension developers to provide guidance as the clock is ticking down.

Re: Proxy Chrome extensions are not going to be usable in MV3

#203

Post by jogu »

cute_boi wrote: post #178
eastendguy wrote: post #75

Earlier quoted context omitted.

There is an easy alternative: Use Firefox

these days many website don't work in firefox. And the worst thing is you never know it was firefox that was causing problem. Last time I tried to login verizon it didn't work. Same with many website I can't remember on top of my head. I still can't leave firefox due to multi containers tho :(

I've found that many times when a site doesn't work in Firefox it's actually extensions causing issues rather than Firefox itself. That being said, there are still compatibility issues from time to time!

Re: Proxy Chrome extensions are not going to be usable in MV3

#204

Post by esperent »

erklik wrote: post #191
esperent wrote: post #186

Earlier quoted context omitted.

What if product B is also bad? And there's also a product C, D, E but when you check them out you realize they are essentially clones of product A?

Firefox is a legitimate alternative, it works for >99% of the world's websites and is an actual alternative i.e. not a clone of Chrome. I've been using it for nearly the last 5 years full-time and have never needed to open Chrome. I am not sure how one can pretend otherwise, so no, I don't think just saying it's "bad" and ignoring it as an alternative is viable. Do some Google websites perform worse on Firefox? Sure,…

> If the audience of HN is not able to make that sacrifice (not use some of the GOOG's website) then we deserve the monopoly of Chrome.

The audience of HN is unlikely to make a difference here.

Besides, we are not some political party who all need to vote in one way together. Each person individually here makes their own choices.

Personally I think making my life harder with pointless sacrifices is not useful. I ask myself, am I making this sacrifice to make myself feel good, or because I actually think it can make a change? In this case, I don't think it would make any difference and it wouldn't make me feel good so there's no utility in using Firefox, for me.

This subject - browser monopoly, and related things like OS or app store monopoly - needs to be tackled with regulation, not personal sacrifices.

Re: Proxy Chrome extensions are not going to be usable in MV3

#205

Post by erklik »

esperent wrote: post #204
erklik wrote: post #191

Earlier quoted context omitted.

Firefox is a legitimate alternative, it works for >99% of the world's websites and is an actual alternative i.e. not a clone of Chrome. I've been using it for nearly the last 5 years full-time and have never needed to open Chrome. I am not sure how one can pretend otherwise, so no, I don't think just saying it's "bad" and ignoring it as an alternative is viable. Do some Google websites perform worse on Firefox? Sure,…

> If the audience of HN is not able to make that sacrifice (not use some of the GOOG's website) then we deserve the monopoly of Chrome. The audience of HN is unlikely to make a difference here. Besides, we are not some political party who all need to vote in one way together. Each person individually here makes their own choices. Personally I think making my life harder with pointless sacrifices is not useful. I ask…

> The audience of HN is unlikely to make a difference here.

The audience of HN and devs in large, are the ones who've contributed to the monopoly of Chrome. Us only testing and creating applications for Chrome led to this.

I never said that people don't make their own choice. Of course they do. My point was that if we are going to complain about Chrome, then Firefox is a perfectly fine alternative and is currently the best way to change GOOG's ways is by voting with our feet.

Would regulation be nice? Sure. I doubt it's coming though so for the moment, our only alternative to not living in a ad-infested hellscape is to use Firefox.

Re: Proxy Chrome extensions are not going to be usable in MV3

#206

Post by DangitBobby »

devwastaken wrote: post #107
pessimizer wrote: post #72

Earlier quoted context omitted.

You haven't applied Hanlon's Razor properly. They're just coordinating incompetence that they find beneficial, not being malicious.

Someone in authority said or inferred some version of "don't talk about this, don't get involved". That's malicious.

I think it's more likely that no one wanted to take ownership of it, so no one did.

Re: Proxy Chrome extensions are not going to be usable in MV3

#207

Post by tbodt »

dotproto wrote: post #193
HellsMaddy wrote: post #125

Manifest V2 deprecation is likely going to break extensions that inject userscripts, like Tampermonkey [0] and SurfingKeys [1]. The Chrome team has been rather unhelpful. They've promised to add support for power-user tools like these in MV3: dotproto from the Chrome team commented on May 27 [2]: > @mon-jai, the short answer is no, I don't have any updates to share. That said, I'll reaffirm that we plan to support us…

Hey, I'm that Simeon/dotproto guy! We discussed Chromium's current plan to support user scripts managers in Manifest V3 during our WebExtensions Community Group (WECG) session at TPAC[1] last week. The notes for that meeting haven't been merged yet, but there's an open PR[2] and when they are they will live here[3]. In short, the current plan in Chromium is to require end users and extension authors to opt into execu…

If chunks of functionality are missing from MV3 with no available alternative, if the replacement is really at such an early stage of development like this, it would be silly not to delay mandatory adoption by another year or two. (Including requiring new extensions to be MV3 - from what I'm reading here, it sounds like you're really not ready for that and should undo it.) Please don't be another https://goomics.net/50/. It's so much worse when it happens externally in an ecosystem.

Re: Proxy Chrome extensions are not going to be usable in MV3

#208

Post by jacooper »

Schroedingersat wrote: post #194
teawrecks wrote: post #146

Earlier quoted context omitted.

I'm out of the loop. I've been using FF for years without any issues across multiple OSes and devices. I plan to continue doing that. I simply don't understand the negative sentiment I see about it, it's served me very well.

The negative sentiment is advertising for brave (an advertising company) to get people to switch to their ad delivery software.

Yeah, when someone disagrees with your opinion, he paid to do so.

Brave ads aren't even enabled by default.

Re: Proxy Chrome extensions are not going to be usable in MV3

#209

Post by glenstein »

okasaki wrote: post #163
glenstein wrote: post #162

Earlier quoted context omitted.

I just looked at all of those images and I'm not sure what point you're making? The links you shared look about how I would expect them to look at 150% zoom. Are you saying it has unusual default settings, and that 150% zoom is one of them? For what it's worth in my experience of installing Firefox which are probably done half dozen times in the past year or so on various devices, I haven't experienced anything like…

Is this a joke? The only things correctly sized are the page and the hamburger menu. Do you not see the oversized tab-bar, the tiny icons on the tab-bar and address bar, the tiny ublock origin dialog, and the huge settings page?

I see all of those things, and none of them look unusual. Contrary to your claim, the tab part is not appear oversized but rather a normal size, contrary to your claim the icons also look a normal size, the address bar looks normal size and ublock origin looks the normal size and the settings page looks more or less normal.

It's hard to understand what you think is unusual. Everything in the browser is displayed normally. The page is different because you used a different zoom, and it zoomed the way Page is normally do.

Are you suggesting that the browser tab bar and settings pages should also grow or shrink if you zoom in or out on a particular web page inside of a tab?

I think you're not fully appreciating how unclear you're being with all of this.

Re: Proxy Chrome extensions are not going to be usable in MV3

#210

Post by Smar »

cute_boi wrote: post #178
eastendguy wrote: post #75

Earlier quoted context omitted.

There is an easy alternative: Use Firefox

these days many website don't work in firefox. And the worst thing is you never know it was firefox that was causing problem. Last time I tried to login verizon it didn't work. Same with many website I can't remember on top of my head. I still can't leave firefox due to multi containers tho :(

I've also seen sites that do not work in Chrome.
Post reply on HN