News for hackers. Stuff that matters.
Re:Google sets burial date for legacy Chrome Extensions, fea... by erklik on Tuesday September 28, 2021 @03:17AM (#28680147)
It's time for mass-migration to Firefox. Only losing users is going to tell Google that this is a horrible solution to enforce.
Re:Google sets burial date for legacy Chrome Extensions, fea... by vadfa on Tuesday September 28, 2021 @03:20AM (#28680166)
The only browser that's been losing users for years is Firefox. That already tells Google all they need to know. (It also tells Mozilla what they need to know; pity they are deaf.)
Re:Google sets burial date for legacy Chrome Extensions, fea... by erklik on Tuesday September 28, 2021 @03:26AM (#28680195)
Mozilla annoys me. Truly it does. However, it's the organisation.

Firefox as a browser, especially dev tools, seems better in every day use than Chrome does. I am really not sure why they keep losing users. I do remember being massive performance issues in the past, but that's really not the case today (at least in my experience)

Re:Google sets burial date for legacy Chrome Extensions, fea... by ChuckNorris89 on Tuesday September 28, 2021 @03:41AM (#28680276)
>I am really not sure why they keep losing users.

Because, number one, they keep constantly making radical UI/UX changes that frustrate and alienate their long term users who would rather they keep the "older look" which they got used to and works just fine for them, and number two, most websites are lazy so their devs only optimize for Chrome, even going the extra mile to explicitly state that "For best experience use Chrome" <face_palm>

Edit: changes in tone and corrections after getting off the bus

Re:Google sets burial date for legacy Chrome Extensions, fea... by RheingoldRiver on Tuesday September 28, 2021 @04:00AM (#28680351)
> Because they keep making stupid UI)UX choices than alienate their users

Cannot overstate this enough. They keep randomly changing their UI constantly, and it's especially frustrating when you have a bunch of custom CSS. I'm a bunch of versions behind & dreading updating because I don't want to spend the hours it'll take to fix my shit for their new version. I honestly hate this browser so much at this point, but everything else (i.e. Chrome) is so much worse that I'm stuck....

Re:Google sets burial date for legacy Chrome Extensions, fea... by yesenadam on Tuesday September 28, 2021 @04:50AM (#28680607)
I don't want to update, when the update is to something that looks horrible. (Last update I spent hours googling for scripts to reverse the appearance changes. Seems there were 1000s of people looking for the same thing!) But in FF preferences there are only 2 choices.

1. Automatically install updates (recommended)

2. Check for updates but let you choose to install them

You would think I'd choose option 2, since I don't want updates, but I tried that, and I got a popup several times a day saying INSTALL UPDATE NOW OR LATER—no way to say "No I don't !%$@ want to update!" ... so after putting up with that for a while I changed to option 1 to avoid the neverending update popups. Not at all what I want though. Talk about a dark pattern. "let you choose to install them" indeed! Not "choose whether to install" but "bombard you with update popups until you crack and choose to install".

Re:Google sets burial date for legacy Chrome Extensions, fea... by estebank on Tuesday September 28, 2021 @06:15AM (#28681074)
Not wanting to install browser updates is no different to asking "how do I turn this yellow light in my car's dashboard? I know! I'll put tape over it!". Granted, the update might come with UI changes. Changing oil in your car won't do that. That can be annoying, but whether something looks "horrible" is completely subjective. That's fine. You can rely on userChrome.css[1] to customize things more in Firefox than in any other browser.

Personally, I've gone from "customize every last pixel" to just using things the way the designers wanted me to use things. I like having flexibility and configuration toggles, that I use often, but I'm much happier now without trying to customize things for customization's sake.

[1]: https://www.userchrome.org/firefox-89-styling-proton-ui.html

Re:Google sets burial date for legacy Chrome Extensions, fea... by yesenadam on Tuesday September 28, 2021 @06:51AM (#28681285)
I take issue with almost everything you said. Sorry my reply is too brief. It's "no different to"..what?! I don't agree that whether something looks "horrible" is completely subjective. I've never tried to customize things for customization's sake, if you're implying I do? Not sure. I used userChrome.css once I think, and as I didn't know about its existence beforehand, it took me hours to fix FF.
Re:Google sets burial date for legacy Chrome Extensions, fea... by estebank on Tuesday September 28, 2021 @08:44AM (#28682083)
> It's "no different to"..what?!

Having an out of date browser is as "dangerous" to you and those around you as driving in a car with flat tires. Declining to upgrade software because of aesthetic changes seems shortsighted to me.

> I don't agree that whether something looks "horrible" is completely subjective.

Let's agree to disagree.

> I've never tried to customize things for customization's sake, if you're implying I do?

I'm not saying you have, I'm saying I have customized things for change's sake, and since I stopped doing that and being overly annoyed and fighting changes "forced" on me, I adapted to most of those changes. I dislike when customization options are taken away. But I also understand that customization comes at the bottom of priorities of developers, and that is likely the right call to make for most applications.

It is a problem that upgrades aren't always an improvement on every axis, but staying on old network connected applications is manifestly not a reasonable solution.

Re:Google sets burial date for legacy Chrome Extensions, fea... by marssaxman on Tuesday September 28, 2021 @01:27PM (#28685245)
> Having an out of date browser is as "dangerous" to you and those around you as driving in a car with flat tires. Declining to upgrade software because of aesthetic changes seems shortsighted to me.

If the browser designers think it's so important for people to update, then perhaps they should stop driving people away with relentless, needless, irritating aesthetic changes! They're the short-sighted ones here.

Re:Google sets burial date for legacy Chrome Extensions, fea... by marssaxman on Tuesday September 28, 2021 @01:25PM (#28685233)
I have also given up tweaking the interface, long ago. I wish Mozilla's devs could learn the same lesson.

You might tape over the warning light on your car's dash too, if you knew there was a good chance it would come back from the shop painted a different color and having had a racing spoiler bolted onto the trunk.

Re:Google sets burial date for legacy Chrome Extensions, fea... by mnadkvlb on Tuesday September 28, 2021 @06:10AM (#28681053)
I had exact same experience. changed the registry settings in windows and am fine. Didn't have the nerves to find how to do on my mac and am just clicking discard every time. Annoying indeed. i wonder most of this shit is probably from the mozilla funding requirements to nerf the browser.

For eg. why tf would you put a separate scroll menu on tab right click to close tabs on left or right, it saves literally 1 row. and increases every single tab change to two clicks. UI disaster!!

i hope some group forks firefox and i will happily donate. But, due to current mozilla ceo siphoning money, not gonna donate a penny.

Re:Google sets burial date for legacy Chrome Extensions, fea... by irthomasthomas on Tuesday September 28, 2021 @05:11AM (#28680717)
Sniff your browser traffic to figure out which url they use to poll for updates and block that on your router or firewall. If that doesn't work, maybe you can redirect it in hosts file, and spoof the response to say there's no new updates.
Re:Google sets burial date for legacy Chrome Extensions, fea... by yesenadam on Tuesday September 28, 2021 @05:53AM (#28680955)
Thank you.
Re:Google sets burial date for legacy Chrome Extensions, fea... by irthomasthomas on Tuesday September 28, 2021 @06:24AM (#28681128)
I think you can also do it with an enterprise policy flag

https://github.com/mozilla/policy-templates/blob/master/READ...

Re:Google sets burial date for legacy Chrome Extensions, fea... by readflaggedcomm on Tuesday September 28, 2021 @05:12AM (#28680728)
FWIW forums like reddit's r/FirefoxCSS usually have solutions as soon as changes roll out on Developer Edition, which is months ahead of the release. It was like that for the ugly new tabs, for instance, which I never had to deal with.
Re:Google sets burial date for legacy Chrome Extensions, fea... by yesenadam on Tuesday September 28, 2021 @05:50AM (#28680939)
Thanks, yeah, that's where I ended up last time hehe. I should've just asked about it on HN, of course.
Re:Google sets burial date for legacy Chrome Extensions, fea... by addingnumbers on Tuesday September 28, 2021 @01:05PM (#28685009)
Have you considered their extended support release (ESR)?

> Firefox Extended Support Release (ESR) is an official version of Firefox developed for large organizations like universities and businesses that need to set up and maintain Firefox on a large scale. Firefox ESR does not come with the latest features but it has the latest security and stability fixes.

https://support.mozilla.org/en-US/kb/switch-to-firefox-exten...

Re:Google sets burial date for legacy Chrome Extensions, fea... by mfo4321 on Tuesday September 28, 2021 @06:17AM (#28681090)
You can create a policies.json file with these contents:

  {
    "policies": {
      "DisableAppUpdate": true
    }
  }
Place it in the platform specific place: "On Windows, create a directory called distribution where the EXE is located and place the file there. On Mac, the file goes into Firefox.app/Contents/Resources/distribution. On Linux, the file goes into firefox/distribution, where firefox is the installation directory for firefox, which varies by distribution or you can specify system-wide policy by placing the file in /etc/firefox/policies."

from https://github.com/mozilla/policy-templates/blob/master/READ...

EDIT: alternatively, you can install the ESR version for 91, use the userchrome link in the sibling comment, and forget about it for 18 months, wich is what I'm currently doing. And good thing too, apparently 92 broke some UI again, because of course it did.

Re:Google sets burial date for legacy Chrome Extensions, fea... by ikt on Tuesday September 28, 2021 @04:54AM (#28680627)
but you recognise you are in likely a sub 0.5% of users with custom css?

chrome gained a lot for two reasons, it was a hell of a lot better than firefox and they advertised the crap out of it.

Firefox has caught up significantly since then but doesn't have the advertising

the adblock debate will push a lot of users back to firefox and it feels like the ui is in a much better place than it was

Re:Google sets burial date for legacy Chrome Extensions, fea... by pessimizer on Tuesday September 28, 2021 @08:29AM (#28681988)
> but you recognise you are in likely a sub 0.5% of users with custom css?

People don't want to do custom CSS, they have to in order to get the workflow back that they had last week. It's annoying and a lot of work. Firefox changes probably cause >3% user attrition every single release.

Re:Google sets burial date for legacy Chrome Extensions, fea... by asdff on Tuesday September 28, 2021 @01:10PM (#28685062)
>It's annoying and a lot of work.

Not anymore. There are github lists documenting everything you can do with css in firefox these days. And I don't think the answer to your workflow being disturbed is to nuke the entire thing from orbit and built it back up on another platform, that sounds a lot harder than skimming these github pages.

Re:Google sets burial date for legacy Chrome Extensions, fea... by 5560675260 on Tuesday September 28, 2021 @10:26AM (#28683173)
I've heard this justification numerous times. Yes, there might be only 0.1%-5% users relying on any given UI feature, but with a constant stream of poorly thought out changes and feature cuts Mozilla will keeps pissing off more and more users until none are left.
Re:Google sets burial date for legacy Chrome Extensions, fea... by throwaway14356 on Tuesday September 28, 2021 @05:05AM (#28680683)
i tried maybe 300 extensions back in the days. Some 30 or so turned out useful enough to keep (for maxthon it was around 60)

today non of these extensions exist and similar things are a joke by comparison lacking the large userbase and years of refinement.

then i also frequently have no idea where most of the interface buttons have gone.

i still use it but im far from locked into the ecosystem.

Re:Google sets burial date for legacy Chrome Extensions, fea... by RheingoldRiver on Tuesday September 28, 2021 @05:30AM (#28680828)
Honestly at this point I just miss the api that let you get tab-specific history which enabled MouseGestures to show a context menu on right-click scroll-up/down to go forward-back in current tab. It seems like such a minor thing that there's no reason not to support, and such a huge QOL to keep around. I feel the lack of it on a weekly basis like a decade (?) after it was removed, I'm never gonna get used to not having it.
Re:Google sets burial date for legacy Chrome Extensions, fea... by zuhsetaqi on Tuesday September 28, 2021 @05:03AM (#28680677)
Can you give some examples what you changed? I’m very curious because I’ve never heard about it and can’t imagine what people would do with it
Re:Google sets burial date for legacy Chrome Extensions, fea... by RheingoldRiver on Tuesday September 28, 2021 @05:26AM (#28680803)
Sure! I use a single toolbar at the top that contains back/forward, refresh/stop, menu dropdowns (which are all hidden except for History/Bookmarks/Tools), the address bar, my bookmarks toolbar buttons, and all addon buttons. Below that is my tab toolbar. This setup is accomplished by CSS with a bunch of position:absolute; and negative margins and stuff, because it's impossible to truly have all of these things in the same toolbar physically. Every single time they change stuff, it gets screwed up.

Prior to their rewrite of everything in version fifty-whatever, I could just drag-and-drop all this stuff into a single toolbar, but when they decided they knew better than me how I want my browser to look it all got 100x harder to get the layout I want.

In addition to this single-toolbar layout I have some easy stuff like highlighting the background color of "View background image" and "Copy link location" and I think 2-3 other things in the context menu a dark purple so that I misclick less often (this particular change is actually amazing and I highly recommend it!).

And I make the URL dropdown suggestions constrained to the width of the URL bar, not 100%, because I find the context switching of hiding the entire webpage too jarring when they're that wide. And I also hide a bunch of random buttons here and there that I find useless; I'm not sure what they are at this point because they've been hidden for so long...

Oh! And my highlight color (in URL bar, etc) is bright magenta (otherwise my theme is dark mode). Just because I like it. :) I use that in Sublimetext too, though I don't do that in every text editor/IDE.

Re:Google sets burial date for legacy Chrome Extensions, fea... by ohgodplsno on Tuesday September 28, 2021 @07:13AM (#28681424)
Don't reverse responsibilities. _You_ made the choice of changing this CSS. _You_ fucked the layout up when the upgrade comes in.
Re:Google sets burial date for legacy Chrome Extensions, fea... by pessimizer on Tuesday September 28, 2021 @08:26AM (#28681968)
From the description, it looks like they unfucked the layout, then firefox refucked it.

A decade ago it was very easy to make Firefox look like you wanted, even without extensions (if you weren't opinionated about aesthetics, just position and functionality.) Every UI change since Chrome was released has been a regression, and more obnoxiously, each change has been locked in with user adjustment actively prevented or made prohibitively difficult, even for programmers.

They could at least offer a consistent interface to change the UI. Instead they demand the flexibility to make UI changes without having to maintain an interface, while using that flexibility to claw back more and more flexibility from their users.

Re:Google sets burial date for legacy Chrome Extensions, fea... by asdff on Tuesday September 28, 2021 @01:06PM (#28685017)
pretty sure it was one boolean in my about:config to disable proton and revert the old UI. Not that hard if you already are wonking with custom css.
Re:Google sets burial date for legacy Chrome Extensions, fea... by op00to on Tuesday September 28, 2021 @07:11AM (#28681415)
What do you have to fix when you upgrade?
Re:Google sets burial date for legacy Chrome Extensions, fea... by ohgodplsno on Tuesday September 28, 2021 @07:11AM (#28681410)
People like you editing their userChrome.css should never be taken into account when it comes to UI changes. It comes with dozens of warnings that it is not an officially supported thing to do so, it's just left accessible should you want to at your own risk, and when said risks happen, you blame Mozilla for it? Get real.
Re:Google sets burial date for legacy Chrome Extensions, fea... by quonn on Tuesday September 28, 2021 @03:53AM (#28680314)
I think the UI is finally good on macOS. The only thing I find strange now is the button-like tab style. Which seems like a minor issue.
Re:Google sets burial date for legacy Chrome Extensions, fea... by ntp85 on Tuesday September 28, 2021 @05:03AM (#28680667)
So do I. The UI also looks pretty good on GNOME.
Re:Google sets burial date for legacy Chrome Extensions, fea... by blitzar on Tuesday September 28, 2021 @05:21AM (#28680776)
But does it still halve my battery life?
Re:Google sets burial date for legacy Chrome Extensions, fea... by tfehring on Tuesday September 28, 2021 @05:44AM (#28680905)
Yes, at least as of a month ago.
Re:Google sets burial date for legacy Chrome Extensions, fea... by asdff on Tuesday September 28, 2021 @01:11PM (#28685077)
you can even disable all that if you want. its completely customizable.
Re:Google sets burial date for legacy Chrome Extensions, fea... by marssaxman on Tuesday September 28, 2021 @01:21PM (#28685182)
I have come to dread that little firefox update notification because of the relentless, pointless UI churn. I wish they would just leave well enough alone. There's no way I would use Chrome, though, so I'm stuck with it.
Re:Google sets burial date for legacy Chrome Extensions, fea... by asdff on Tuesday September 28, 2021 @01:07PM (#28685033)
You can revert back to the old quantum ui with a toggle for proton in your about:config
Re:Google sets burial date for legacy Chrome Extensions, fea... by tut-urut-utut on Tuesday September 28, 2021 @03:40AM (#28680273)
They just can't compete with Google and their massive marketing budget and shady bait & switch business practices.
Re:Google sets burial date for legacy Chrome Extensions, fea... by chii on Tuesday September 28, 2021 @04:16AM (#28680431)
i dont think it's merely marketing budget, thought that helps.

People who got marketed to convert, and hence, the product is indeed good based on this metric.

Firefox does seem to lag behind in terms of performance, esp. on mobile. Firefox also has poorer video rendering speed i think - i get more skipped frames than chrome. I tolerate it, but many users don't.

Firefox has some difficulty being deployed in an enterprise environment (aka, an organizationally managed profile, which chrome has). This has led to enterprises adopting chrome as a primary browser (over firefox), and this may lead to familiarity which causes them to also use chrome at home.

There's a myriad of issues with firefox, and it is rooted at the organizational level, rather than the technical level, but these issues bleed down into the technical level.

Re:Google sets burial date for legacy Chrome Extensions, fea... by rejectfinite on Tuesday September 28, 2021 @12:04PM (#28684386)
>Firefox also has poorer video rendering speed i think - i get more skipped frames than chrome. I tolerate it, but many users don't.

I do not have this problem in Firefox anymore. I used to but i updates fixed it.

>Firefox has some difficulty being deployed in an enterprise environment (aka, an organizationally managed profile, which chrome has). This has led to enterprises adopting chrome as a primary browser (over firefox), and this may lead to familiarity which causes them to also use chrome at home.

GPO exists for Firefox now and works great, I have implemented it.

But what I actually see for enterprise customers is a move to MS Edge. The Windows account integration, control and the fact that on Windows 10 it has really good performance means there is no need for Chrome or FF unless Edge breaks (have had some issues with antivirus breaking it)

Re:Google sets burial date for legacy Chrome Extensions, fea... by vadfa on Tuesday September 28, 2021 @04:04AM (#28680370)
Almost all wounds Mozilla has are self-inflicted.
Re:Google sets burial date for legacy Chrome Extensions, fea... by josefx on Tuesday September 28, 2021 @12:11PM (#28684439)
On Android Chrome has to be installed as preferred browser or the phone manufacturers get blocked from Googles other services. As much as I like to bash Mozillas leadership, Google has taken every shady (and sometimes illegal) shit 90s era Microsoft pulled and turned it up to eleven.
Re:Google sets burial date for legacy Chrome Extensions, fea... by jacquesm on Tuesday September 28, 2021 @04:11AM (#28680397)
They could, if they stopped doing all of their hobby stuff.
Re:Google sets burial date for legacy Chrome Extensions, fea... by hutzlibu on Tuesday September 28, 2021 @04:27AM (#28680482)
"Firefox as a browser, especially dev tools, seems better in every day use than Chrome does. "

Cannot confirm at all. I do not know any feature in ff dev tools I am missing in chrome, but the other way around lots of it.

Mainly: editing and saving directly in the debugger!

Could also be my ignorance, but I regulary do debugging in FF and it works, but way less efficient.

Meaning I browse with FF, but work with chrome.

Re:Google sets burial date for legacy Chrome Extensions, fea... by yfkar on Tuesday September 28, 2021 @05:11AM (#28680718)
One thing where I've used Firefox devtools instead of Chrome is when debugging font usage (which is not very often).

Chrome tells you the used font for a single element on a pretty generic level, e.g. "Lato — Local file" or "Lato — Network resource".

Firefox Inspector has a Fonts tab that lets you list all the fonts used on a page. It tells you a more specific font name, e.g. "Lato Regular", the relevant @font-face rule and also the font URL if it's a network resource.

Re:Google sets burial date for legacy Chrome Extensions, fea... by maddyboo on Tuesday September 28, 2021 @04:47AM (#28680598)
I mostly agree, but one really nice feature FF has is the ability to see a diff of the CSS properties you've changed in the inspector:

https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...

Re:Google sets burial date for legacy Chrome Extensions, fea... by marcosdumay on Tuesday September 28, 2021 @10:47AM (#28683456)
> Mainly: editing and saving directly in the debugger!

Hum... Firefox does that. I know because every time I mistakenly start saving I ask what is the point of it. But well, looks like it's useful for somebody.

Re:Google sets burial date for legacy Chrome Extensions, fea... by hutzlibu on Tuesday September 28, 2021 @02:50PM (#28686103)
Erm, it can edit and save code live in a debbing session?

Also, how can I edit code? It is non editable for me.

Re:Google sets burial date for legacy Chrome Extensions, fea... by marcosdumay on Tuesday September 28, 2021 @03:12PM (#28686284)
The Firefox developer version¹ has a full file menu on its code viewer, with save, open, refresh, etc.

I believe you can activate it on the main build too, but I don't know how. Anyway, if you are debugging code, I highly recommend the developer version.

1 - That is a different configuration of the same code as the main build, for web developers. It's not for developing Firefox itself.

Re:Google sets burial date for legacy Chrome Extensions, fea... by maccard on Tuesday September 28, 2021 @05:06AM (#28680691)
But you're ok with google the organization?
Re:Google sets burial date for legacy Chrome Extensions, fea... by krageon on Tuesday September 28, 2021 @05:20AM (#28680773)
> dev tools

Chrome's devtools have been superior (faster, more reliable, more featureful) for years near as I can tell (and everyone I work with). I am curious what makes you feel firefox's devtools are better.

Re:Google sets burial date for legacy Chrome Extensions, fea... by k_ on Tuesday September 28, 2021 @05:28AM (#28680819)
Alternative take: [dev]tools are only as powerful as how well you know them. I'd like to think both firefox devtools and chrome devtools as highly capable, but you'll get way more out of the one you're used to, whichever it is.
Re:Google sets burial date for legacy Chrome Extensions, fea... by Jach on Tuesday September 28, 2021 @05:48AM (#28680931)
Another alternate take: everything since Firebug has been cake icing, what differences there are now on top of that base feature set are minimal.
Re:Google sets burial date for legacy Chrome Extensions, fea... by krageon on Tuesday September 28, 2021 @07:34AM (#28681569)
The two devtools purport to do almost the exact same things, with a practically identical interface. The details are where the usability differences lie, such as chrome's vastly superior formatting/debugging story. I only moved to Chrome after working with firebug (!) for years and then working with firefox's builtin devtools. If anything, I should hate Chrome's devtools the most because I know them least well.
Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @03:54AM (#28680318)
I wonder why. It's not like Firefox is a bad browser.
Re:Google sets burial date for legacy Chrome Extensions, fea... by chii on Tuesday September 28, 2021 @04:23AM (#28680463)
> It's not like Firefox is a bad browser.

compared to chrome, firefox no longer has an edge. Chrome's restrictive addons is what made firefox stronger.

But ever since firefox removed the old XUL style addons, their utility has drastically dropped against chrome. I was very angry at their poor choice, as some really excellent, but unmaintained addons no longer work.

I put up with firefox, just so i can give them some boost (whatever that might amount to), but obviously not that many users would sacrifice their browsing experience for such purposes.

Firefox should be the premier customizable browser, with more addons than chrome. Instead, firefox chose to copy chrome. Thus, it is forever relegated to being second.

Re:Google sets burial date for legacy Chrome Extensions, fea... by progval on Tuesday September 28, 2021 @04:54AM (#28680623)
I also hate they had to kill XUL addons, but they had good reasons to do so: https://yoric.github.io/post/why-did-mozilla-remove-xul-addo...
Re:Google sets burial date for legacy Chrome Extensions, fea... by chii on Tuesday September 28, 2021 @05:01AM (#28680659)
Those aren't good reasons from the user's perspective. Those reasons were good reasons from a technical, and maintenance perspective (which, as a software engineer, i understand). Those reasons are what engineers give to product management in order to get a green-field rewrite.

But firefox's value add is their addon system - even if it is old, and difficult to use. It enabled some really great addons that weren't possible in the new replacement (as a simple example, the DownThemAll was rewritten using this new api, and it's shadow of their former self).

Firefox should have paid the cost to maintain the old legacy system, and replace it only when the webextensions api is sufficient to replace _all_ functionality (which, of course, won't because webextensions evolved from google trying to kill off addons https://developer.chrome.com/docs/extensions/reference/ ).

Re:Google sets burial date for legacy Chrome Extensions, fea... by imbnwa on Tuesday September 28, 2021 @01:15PM (#28685115)
Not to mention XULRunner/XPCOM was Electron before Electron. I remember using the Songbird app, as well as an IM client whose name I can't recall now, across Windows and Linux back in the 00s. So They literally decided to cede the cross-platform browser-based desktop software framework du jour to Chromium.
Re:Google sets burial date for legacy Chrome Extensions, fea... by MomoXenosaga on Tuesday September 28, 2021 @09:52AM (#28682791)
When they explained it I actually agreed with the changes. But that was on the condition that those extensions would be coming back.

But it's been years now and Mozilla's only solution is to switch to nightly.

Re:Google sets burial date for legacy Chrome Extensions, fea... by MomoXenosaga on Tuesday September 28, 2021 @04:52AM (#28680614)
Yes this is true. Mozilla neutered extensions on Android.

I'm using Firefox nightly and I have to jump through hoops to get the extensions I want. Far too complicated for most users I'm sure.

Re:Google sets burial date for legacy Chrome Extensions, fea... by tjpnz on Tuesday September 28, 2021 @05:03AM (#28680676)
On Android it's freaking fantastic. Everything feels snappier and I can utilise uBlock Origin to block all of the BS. I've set this up for family, friends etc and none have gone back to Chrome. I think the biggest issue is marketing.
Re:Google sets burial date for legacy Chrome Extensions, fea... by iggldiggl on Tuesday September 28, 2021 @07:34AM (#28681565)
The total rewrite might have given some performance boost and if that's worth it for you then I'm glad for you, but unfortunately it also caused loads of bugs and features that have gone missing, and now that the big push for the rewrite is over, tackling those remaining bug fixes and missing features is again happening at a rather glacial rate.

And the frustrating thing is that this used to be a problem even with the previous iteration of Firefox on Android, i.e. it seemed somewhat understaffed and had some surprising bugs (e.g. under memory pressure it would suddenly and silently stop remembering your current tabs) and missing functionality (it didn't remember your scroll position if the app was killed, you couldn't reorder tabs in the tab list) that were only fixed after years, and even then quite a few times only through outside contributions.

And now the rewrite means that all of this has been thrown away and judging from the current development speed it'll take once more years until we sort of get back to where we used to be.

Re:Google sets burial date for legacy Chrome Extensions, fea... by Mirioron on Tuesday September 28, 2021 @05:16AM (#28680744)
Have they fixed the scrolling? For years the scrolling in mobile Firefox felt bad/off. At one point I just gave up on trying to make it work.
Re:Google sets burial date for legacy Chrome Extensions, fea... by commoner on Tuesday September 28, 2021 @06:02AM (#28681009)
This was fixed for me in November 2017 when Async Pan/Zoom (APZ) was implemented:

https://hacks.mozilla.org/2017/11/async-panzoom-apz-lands-in...

Also, Firefox 79+ on Android (August 2020) performs significantly better than older versions, despite having lost many features in the rewrite. The current version might meet your expectations.

Re:Google sets burial date for legacy Chrome Extensions, fea... by nicoburns on Tuesday September 28, 2021 @07:10AM (#28681406)
Yes. They did a rewrite of the android UI layer that released last year, and since then the scrolling is on par with chrome. If you install ublock origin then Firefox now has the best android browser experience by some way.

(The 2017 update did not do it for me)

Re:Google sets burial date for legacy Chrome Extensions, fea... by prox on Tuesday September 28, 2021 @04:09AM (#28680384)
Not only is it not bad, it’s pretty good. I have been using it for a decade and its fast, superior privacy above Chrome, devtools do everything I need.

I test on Chrome, and I personally don’t think switching is that big a deal that some commenters make it out to be. It’s just as fast as Chrome or faster, the UX is similar enough not be stalled for long if you need to switch. It’s really worth a shot!

Re:Google sets burial date for legacy Chrome Extensions, fea... by chucky on Tuesday September 28, 2021 @08:12AM (#28681862)
What does it tell Mozilla that they need to know? Because I certainly don't understand, but I'm a happy Firefox user so obviously I'm not part of any exodus.
Re:Google sets burial date for legacy Chrome Extensions, fea... by feketegy on Tuesday September 28, 2021 @03:56AM (#28680326)
They don't have any coherent marketing strategy, most people still think that Firefox is this sluggish browser that don't support anything.

Also, most non-technical people use the default browser that's installed on the OS whether that's Safari or Edge.

When manifest v3 kicks in and we'll see the true ad horror that's the Internet today without ad blockers, maybe then we'll jump to a more privacy first browser. Until then nothing will happen.

Re:Google sets burial date for legacy Chrome Extensions, fea... by hutzlibu on Tuesday September 28, 2021 @04:32AM (#28680511)
I pity anyone, surfing the web without adblockers. I am regulary shocked, when I use a browser without one.
Re:Google sets burial date for legacy Chrome Extensions, fea... by GoblinSlayer on Tuesday September 28, 2021 @07:59AM (#28681760)
It's because Chrome is preinstalled on Android, Internet Explorer all over again.
Re:Google sets burial date for legacy Chrome Extensions, fea... by dobladov on Tuesday September 28, 2021 @03:26AM (#28680199)
Is v3 an horrible solution or the deprecation of v2 in 2023?

I ported one of my extensions to v3 and while the process was not completely trivial it did not took more than a few hours, in my opinion the change is worth it this makes extensions more secure.

As far as I know Firefox is also moving to v3, maybe not enforcing it for now, but they will probably deprecate v2 at some point.

Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @03:57AM (#28680332)
The new declarative APIs are great. They will protect user data from potentially malicious extensions.

The thing is uBlock Origin is just so important and trusted that these restrictions shouldn't apply to it. The functionality of uBlock Origin is just so fundamental and unambiguously pro-user it should be integrated into the browsers themselves. Conflicts of interest prevent that unfortunately but the fact remains that browsers without uBlock Origin installed cannot call themselves user agents.

uBlock Origin should just get access to everything so it can do its job as well as it possibly can. For everyone else, there's the standard APIs.

Re:Google sets burial date for legacy Chrome Extensions, fea... by mmis1000 on Tuesday September 28, 2021 @04:30AM (#28680494)
> They will protect user data from potentially malicious extensions.

No, they won't. You can still log requests however you want. The only difference is you can't modify/stop it. So the privacy concern is pure BS.

Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @07:17AM (#28681443)
How so? From what I've read, the whole point of the declarative API is to tell the browser what you want done so that it can do it without letting the extension actually touch any data.

If this doesn't work, then there's no point to the new API.

Re:Google sets burial date for legacy Chrome Extensions, fea... by mmis1000 on Tuesday September 28, 2021 @08:40AM (#28682056)
That's why it is pure bs at first place.

The webrequest api didn't got removed completely, only the part for modify/block request.

Only ad blockers will stole your data and others that logs them however they want will log them nicely? What world are Google's team lives in? Are we even on the same time line?

Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @09:47AM (#28682736)
I see. I agree, that's pure bullshit. Google's intentions are transparent.

Can you confirm the new declarative APIs work as intended? Maybe they do restrict extensions. I agree that it's pointless if they don't remove the older APIs.

Re:Google sets burial date for legacy Chrome Extensions, fea... by BoxOfRain on Tuesday September 28, 2021 @04:28AM (#28680486)
Google is first and foremost an advertising company, it's in their interest to hobble ad blockers as much as possible. Personally I'm hoping that they do, because it'll drive people away from Chrome and nip what's looking increasingly like a monopoly in the bud by driving users to browsers that do support ad blocking.
Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @07:22AM (#28681493)
> it'll drive people away from Chrome and nip what's looking increasingly like a monopoly in the bud by driving users to browsers that do support ad blocking

I certainly hope so. I showed Firefox and uBlock Origin to all my friends and they loved it, especially the fact it blocks YouTube ads. Lots of people simply don't know about this.

Re:Google sets burial date for legacy Chrome Extensions, fea... by BoxOfRain on Tuesday September 28, 2021 @09:34AM (#28682587)
Yeah, I don't really do "tech support" for family members any more because I've not used Windows in such a long time I'm pretty useless at troubleshooting it, but I do take the time to install Firefox and ad blockers on it which is worthwhile even if you don't have an issue with the adtech industry because it reduces the attack surface for malware.
Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @09:56AM (#28682817)
Similar experiences here. I don't know anything about Windows anymore but I'll still install Firerox with uBlock Origin on every computer I come across. People notice that the web is just so much nicer. Most don't understand why, they just know. Malware also stopped being an issue: no more malicious ads for them to click.
Re:Google sets burial date for legacy Chrome Extensions, fea... by input_sh on Tuesday September 28, 2021 @03:42AM (#28680283)
While they're interested in maintaining compatibility with Chrome's v3, there's no standard that forces them to make every single v3 change Chrome does.

v2 also already differs in some ways in which Firefox thinks it makes sense. I'm not scared at all that they're gonna deprecate webRequest.BlockingResponse in favour of declarativeNetRequest, which is the specific API function that adblockers rely on. After all, that function has nothing to do with security, best you could argue is that it's related to performance due to filter lists becoming absurdly long.

Re:Google sets burial date for legacy Chrome Extensions, fea... by dotancohen on Tuesday September 28, 2021 @04:00AM (#28680352)
In the context of `webRequest.BlockingResponse` being a performance bottleneck due to filter lists becoming absurdly long, it does in fact become a security issue.

Filter lists are as long as they are because that is the amount of domains that have demonstrated an interest in harming our security (and for many people, online privacy _is_ physical security). Filterlists are blacklists, not whitelists, so they only grow when well-known entities play foul.

Re:Google sets burial date for legacy Chrome Extensions, fea... by kevingadd on Tuesday September 28, 2021 @03:34AM (#28680236)
An extension API that can't implement ad-blockers properly is an extension API that is broken by design. So yes, it's a horrible solution.
Re:Google sets burial date for legacy Chrome Extensions, fea... by selcuka on Tuesday September 28, 2021 @03:42AM (#28680288)
It's not only a simple Manifest version change. They have also deprecated the webRequest API, which is essential to implement any type of content filter or an ad blocker.
Re:Google sets burial date for legacy Chrome Extensions, fea... by gman83 on Tuesday September 28, 2021 @03:58AM (#28680339)
The day that adblockers stop working on Chrome is the day we'll see that mass-migration.
Re:Google sets burial date for legacy Chrome Extensions, fea... by soundnote on Tuesday September 28, 2021 @05:30PM (#28687767)
People already use Chrome on mobile for the most part, and it has no adblockers whatsoever.

A depressing number of users use the web via the Chrome search bar on their phone, and even if they use a browser they go even to familiar sites by googing them.

Re:Google sets burial date for legacy Chrome Extensions, fea... by mda on Tuesday September 28, 2021 @04:28AM (#28680491)
Which will probably never happen.
Re:Google sets burial date for legacy Chrome Extensions, fea... by mrkramer on Tuesday September 28, 2021 @08:12AM (#28681855)
Yea because of legal antitrust reasons but Google will try to disrupt Ad Blockers as much as they are technically and legally allowed to do.
Re:Google sets burial date for legacy Chrome Extensions, fea... by kovac on Tuesday September 28, 2021 @04:15AM (#28680420)
The only reason I don't use Firefox is mozilla. I will never use it as long as it's under mozilla. I use Vivaldi, choosing to support a smaller, genuine business with no bullshit. I hope they'll eventually to develop their own engine.
Re:Google sets burial date for legacy Chrome Extensions, fea... by 2Gkashmiri on Tuesday September 28, 2021 @04:20AM (#28680452)
What... Is the appeal of brave ? I hear it has crypto and shit but why not install Firefox with ubo and be done with it? I feel the "cool" factor of brave is silly as they are just fueling chromium. Why don't these chromium forks base on Firefox instead and do some leg work with the benefit of helping the internet as a whole ? I hear someone said on hn a long time ago, building on ff is a pita. Well guess what, Firefox folk do nightly builds of a boat load of versions and flavours and shit. Why can't you change a theme and call it a day?
Re:Google sets burial date for legacy Chrome Extensions, fea... by 5560675260 on Tuesday September 28, 2021 @11:01AM (#28683598)
There are several things.

1) There is an integrated ad blocker. It's very convenient because I don't have to worry about adblocking plugin is bought out and is compromised, I don't have to figure out if my uBlock is supposed to be "origin" or not, or if I should go for adGuard or something else. There is no risk of adblocking breaking because of the changes in plugin API.

2) Integrated optional ad network that by default distributes money based on your web usage, but gives you control over spending your ad income. This is the coolest thing about Brave and I really wish it would succeed, but, unfortunately, it's very unlikely without very wide adoption and I just don't see that happening

3) Not developed by Mozilla. That's nice since I can't ethically support them.

Re:Google sets burial date for legacy Chrome Extensions, fea... by approxim8ion on Tuesday September 28, 2021 @12:26PM (#28684608)
1) uBlock Origin has been around and without selling out for 6-7 years now. You don't have to worry that the plugin is bought out but you do have to worry that the browser is. You don't have to figure out which adblocker to use, because there is only one right answer. And it takes barely thirty seconds of effort.

I have no opinion about 2.

3 is fair, but I have similar objections about Brendan Eich.

Re:Google sets burial date for legacy Chrome Extensions, fea... by BrendanEich on Saturday October 02, 2021 @09:01PM (#28733637)
This HN post is about Google breaking uBO by retiring Manifest v2. What then?
Re:Google sets burial date for legacy Chrome Extensions, fea... by soundnote on Tuesday September 28, 2021 @05:39PM (#28687855)
To me:

1. Actual features like tab groups which Firefox killed.

2. Likelihood to actually add features. Firefox used to have unique features I liked a lot, like keyword searches synced via bookmarks, but this is set for deprecation and was removed from mobile. I don't remember when Firefox last gave me a new feature.

3. Adblocking on mobile while not being Firefox, which is interestingly rare.

4. Not being developed by Mozilla. Mozilla's increasingly vehement about woke political activism, and after the tech companies booted Orange Man out of the Internet, Mozilla came out in no uncertain terms saying that they'd like politically partisan platforms to decide what I see on the net. I'd used them for years and promptly noped the fuck out. The organization may be for privacy, but they don't seem to care about other important things, or rather care about them the wrong way. I want my browser maker to make a good tool, not to tell me what to think. Mozilla feels more interested in the latter than the former.

5. Brave focuses on building an alternative foothold on the web, not just providing a browser. A lot of the other browsers' footprint comes from associated web and hardware platforms and the resulting integration conveniences. Brave has a big focus on independent revenue streams, which I like a lot even if I'm not really a fan of the crypto stuff.

Firefox lacks that to a large degree. They do have Pocket, which is good, but their userbase is essentially hostile to Pocket because they have some idiotic pipe dream about a donation-funded, pure and moral FOSS project. Meanwhile Firefox the company is moralistic, not moral, and funded by Google.

Re:Google sets burial date for legacy Chrome Extensions, fea... by rejectfinite on Tuesday September 28, 2021 @12:16PM (#28684488)
On mobile it is really good because of the builtin adblocker + chromium engine makes it very fast. It also has background play on Youtube.

On desktop it is less useful. But probably still better privacy vise than Edge or Chrome.

Re:Google sets burial date for legacy Chrome Extensions, fea... by soundnote on Tuesday September 28, 2021 @05:22PM (#28687692)
It's definitely better privacy wise than Edge. Edge is really good, but sadly uses hardware based browser IDs and doesn't offer end to end encryption for all categories of synced data, and their start page is very chatty. Plus I think they default to having search suggestions on and sending the strokes to Bing.

Brave's browser ID is more ephemeral, it's not hardware based and doesn't persist across restarts, search suggestions are off by default and the default engine is DDG/Brave, and their sync service is end to end encrypted.

Edge is a good product, but not if you like wearing tinfoil hats. If privacy is no object, Edge is probably the best.

Re:Google sets burial date for legacy Chrome Extensions, fea... by 2Gkashmiri on Tuesday September 28, 2021 @01:33PM (#28685306)
You use brave on mobile for background playing YouTube? If you are on android, do you know newpipe exists? Or for vanilla youtuber users, there is vanced.

About mobile adblocking, doesn't Firefox android have ubo and a few more addons?

Re:Google sets burial date for legacy Chrome Extensions, fea... by rejectfinite on Tuesday September 28, 2021 @03:47PM (#28686678)
Yes I also use Youtube Vanced :)

Firefox on android is noticeably slower for me than chromium based browsers.

Re:Google sets burial date for legacy Chrome Extensions, fea... by cinquemb on Tuesday September 28, 2021 @04:51AM (#28680609)
As someone who wouldn't mind if Mozilla post Eich can die under a metadata drone strike (doubly so for google) and will still use my FF fork and avoid chrome/chromium based browsers like the plague, brave, seems like they are willing to build in support for decentralized (to me at least) and p2p web directly into the browser (rather than leave it up to potentially less performant 3rd party extensions which may be ok, but not ideal in ff) than all the crap I have to compile out of ff occasionally.
Re:Google sets burial date for legacy Chrome Extensions, fea... by 2Gkashmiri on Tuesday September 28, 2021 @05:25AM (#28680799)
why cant brave build on top of firefox?
Re:Google sets burial date for legacy Chrome Extensions, fea... by cinquemb on Tuesday September 28, 2021 @06:08AM (#28681038)
See Brendan's response to me last week[0], which I think comes down to feature set they want to support rather than do all the work it would require to build that in servo now (they went from gecko [no public info on this] -> electron -> and now chromium. they would have to migrate from chromium -> servo).

I wish they did, and just cared less about all the other features that were missing from gecko (but that's just be being selfish and not wanting to build out native stuff myself lol)

[0] https://news.ycombinator.com/item?id=28605711

Re:Google sets burial date for legacy Chrome Extensions, fea... by 2Gkashmiri on Tuesday September 28, 2021 @07:30AM (#28681540)
cool. so an excel sheet decided google to be the clear winner in present feature comparison set and instead of helping the community in bridging the gap, they decide to go with the flow. cool. i am fine with my ff
Re:Google sets burial date for legacy Chrome Extensions, fea... by chinathrow on Tuesday September 28, 2021 @04:14AM (#28680409)
I am already here since the Phoenix times. Come over guys!

https://website-archive.mozilla.org/www.mozilla.org/firefox_...

Re:Google sets burial date for legacy Chrome Extensions, fea... by echelon on Tuesday September 28, 2021 @03:42AM (#28680281)
It's time for antitrust breakup of Google.

America's top search engine and America's top internet ads company has the America's top browser and pays to be the default search engine for America's top cell phone?

Re:Google sets burial date for legacy Chrome Extensions, fea... by sneak on Tuesday September 28, 2021 @11:19AM (#28683827)
Firefox is a lot less secure than Chromium.