781–790 of 836 posts
Earlier quoted context omitted.
Self Destroying Cookies is a WebExtension. There are now a couple of forks.
Hopefully one of them can deal with localstorage? Because my 30 mins of using cookie autodelete, leads me to think it isn't as good as self destructing... It doesn't seem to reliably delete cookies unless I click the "clean" button.
https://github.com/Cookie-AutoDelete/Cookie-AutoDelete/issue...
Earlier quoted context omitted.
> I have no problem if the Mozilla Foundation or the Firefox team has different priorities, but say that rather than telling technical people the reason for the changes is because XUL or XPCOM are somehow so hideous the team had no choice. It smacks of dishonesty when everything that you have described here is a problem with procedure not anything technical. Well, some of our priorities with WebExtensions are (not ne…
> I believe that we're moving from something unsustainable to something sane It is only unsustainable because the FF team chose to make the process more difficult than it had to be. This is how what you are saying sounds: 1. We didn't want to break plugins so we involved addon developers 2. The process takes so long that it takes 18 months to introduce any new code 3. Since 2 was so slow we decided instead we would P…
Have a good day.
Chrome: https://i.imgur.com/o8f4ZHp.gifv FF 57: https://i.imgur.com/kaQl5gN.gifv
FF 57 is much slower. Maybe a very specific use case but confirms my experience so far that FF is much slower than Chrome on basically everything.
Earlier quoted context omitted.
> FWIW, Firefox 57 is currently looking like a net loss in terms of security and privacy. A significant number of the extensions people have previously used for blocking or restricting potentially intrusive or dangerous behaviours seem to have been lost, in some cases without equivalent WebExtension alternatives being available. First, I'd like to put things in context. When you write "Firefox 57 is currently looking…
I find it interesting that your instinctive view of privacy seems to be about restricting add-ons. That's certainly a useful thing to do, as we can see from some of the recent sell-outs that have meant once-trusted extensions silently became privacy loopholes. Even so, personally I'm more worried about the privacy implications of tracking and other covert behaviours by web sites/apps, and that's where the extensions…
This definitely makes sense. I know that we have new APIs that make some of it much easier to implement, but I imagine that they still have some limitations (I haven't checked). My hope is that APIs will be progressively extended to remove these limitations.
Regardless, I believe that we're better off with a sane API that add-on developers can trust, that we're going to maintain and extend, rather than with all-powerful stuff that breaks randomly :)
Earlier quoted context omitted.
I didn't have any complaints about speed. Who actually cares about browser speed? But I do care that suddenly, my browser looks completely different, half the functionality I use is missing and there is no way for me to get it back. The fact that this happened as an automatic upgrade without as much as asking me whether or not I want it to happen is not exactly a winning point either. Edit: It seems that I was too ha…
> Who actually cares about browser speed? Millions of people who've switched to Chrome. Including hundreds that have said as much in HN comments over the last 5 years.
I do care very much if you break all of my current extensions and as a result the UI behavior I was used to is gone. It's like being forced to switch to a completely new browsers. If I wanted different browser I could have switched to Chrome years ago, thank you very much. Customization is much more important than speed.
Earlier quoted context omitted.
You forget the big technical issue: many web extension API features that are needed to port old Firefox extensions do not exist yet (e.g. filesystem access) or are conservatively crippled (e.g. adding buttons, menu items, other GUI elements). Your 2-3 months of frantic effort will start not immediately but in a vague future when the Firefox team feels like improving the web extension API. It is fairly obvious from AP…
You're pretty much describing what Firefox has been doing for the past few years. At some point, however, the rest of the world keeps moving and, no matter how painful for everyone involved, it becomes unfeasible to wait for all add-ons to be ported (or even portable).
Without Tab Mix Plus Firefox 57 is not an option for me. Does anyone know of an extension that allows multiple tab rows? Tab Trees and like extensions don't cut it. This is the main reason I never switched to Chrome. It's too bad FF had to abandon it's massive library of legacy extensions for this upgrade. The myriad of extensions is one of FF's main benefits over other browsers. I've happily accepted lower performan…
The toolbar API still lacks the required features to allow multirow. According to bugzilla discussions they might add it somewhere in 2018 :( You can also find contradictory statements from different developers like "this should be handled by addons" vs. "addons should manipulate only the web content not the browser itself" etc. It's a mess so maybe if we users push enough they might understand. See https://bugzilla.…
WTF? Who in their right mind can think that the only reason people installed add-ons was to manipulate the web content? UI is the main differentiating factor between browsers, FF strength was the ability to customize UI for user liking.
Earlier quoted context omitted.
You forget the big technical issue: many web extension API features that are needed to port old Firefox extensions do not exist yet (e.g. filesystem access) or are conservatively crippled (e.g. adding buttons, menu items, other GUI elements). Your 2-3 months of frantic effort will start not immediately but in a vague future when the Firefox team feels like improving the web extension API. It is fairly obvious from AP…
"Betraying users"? 52 ESR isn't going anywhere, and I hope you'll forgive me for finding it a strain upon credulity to imagine that any regularly active HN participant could fail to observe even one of the many front-page articles over the past year which have talked about Firefox 57's breaking changes. If it means that much to you, stay on 52 for a year or two, until the extension API and ecosystem have had some tim…
Some very important extensions have fortunately been able to pressure Firefox into supporting them, but the typical Firefox user who depends on some niche extensions has no clout.
1) Is it possible to change the shortcut for Private window to CTRL Shift N somehow like in Chrome? (instead of Ctrl Shift P). (I like that I could use that shortcut with my left hand (albeit with some nice thumb extension action).) 2) Any way to remove the bottom bar icons when the omni bar completion box shows? ... wait... How do I even edit search engines in Firefox? Like say, typing "yt (space) search term" to do…
2) https://support.mozilla.org/en-US/kb/how-search-from-address...
Earlier quoted context omitted.
It looked great, up to the point that 70% of my addons were disabled. I rolled back in 5mins :) I'll give it another chance in a couple of weeks, and hope that there will be a bypass that will force my outdated addons to work.
So while I'm still waiting on NoScript to get an update which is actually forthcoming (possibly tomorrow, but within about a week from what I gather), I took a look around to see which of my other add-ons were updated. Other than a couple that were useful but ultimately not that important, and a couple I can do without until they get updated eventually, I managed to find that most of my Legacy extensions do have upda…