Live data from Hacker News

Firefox 57.0 Released

mozilla.org

761–770 of 836 posts

Re: Firefox 57.0 Released

#761

Earlier quoted context omitted.

Tree Style Tab is available on Firefox Quantum and will be with us for a long, long time. Piro, the author, wrote an excellent article about his experience porting TST to a WebExtension: http://piro.sakura.ne.jp/latest/blosxom/mozilla/extension/tr...

I got the new Tree Style tabs installed, but I'm still seeing the standard tabs at the top, is there a way to hide those?

What uglycoyote commented is the stopgap solution for now, but an API for doing that is in the works, so in a few versions from now, you shouldn't need that more-or-less hack anymore.

Re: Firefox 57.0 Released

#762
post #637

Earlier quoted context omitted.

> Decades of UI/UX knowledge, down the drain. Usability is gone. Exactly the opposite; this is an evolution that has been taking place over the past decade. Firefox has had tabs-on-top as the default since Firefox v4.0 [1]. Chrome has had tabs-on-top for its entire existence (starting in Sept 2008); Opera had them before Chrome. The merits can be argued either way, but don't act like this is sudden or arbitrary; it's…

De gustibus non est disputandum The idea that someone else can know what another wants better than the other person is absurd. Your arguments might be valid for defaults , but they must be configurable defaults , because taste is subjective, arbitrary, and, despite what some believe, never in error . I know what UX I want better than anyone else. Nobody can gainsay my personal taste.

Or maybe they just do and you're just wrong

We don't have a configuration to put the clutch pedal on the right side

Do we?

Re: Firefox 57.0 Released

#763
post #637

Earlier quoted context omitted.

> Decades of UI/UX knowledge, down the drain. Usability is gone. Exactly the opposite; this is an evolution that has been taking place over the past decade. Firefox has had tabs-on-top as the default since Firefox v4.0 [1]. Chrome has had tabs-on-top for its entire existence (starting in Sept 2008); Opera had them before Chrome. The merits can be argued either way, but don't act like this is sudden or arbitrary; it's…

De gustibus non est disputandum The idea that someone else can know what another wants better than the other person is absurd. Your arguments might be valid for defaults , but they must be configurable defaults , because taste is subjective, arbitrary, and, despite what some believe, never in error . I know what UX I want better than anyone else. Nobody can gainsay my personal taste.

Besides, de gustibus non est disputandum doesn't mean what you think

It means that is useless to discuss about other living being tastes, not that Mozilla should provide every single configuration you want

In this case you're the Romans eating the asparagus with the butter in Milan while in Rome they preferred olive oil and Mozilla is the Milanese host serving you the butter asparagus

In Italy we have a say: "you either eat this soup or you jump out of the window"

Re: Firefox 57.0 Released

#764
post #88

Earlier quoted context omitted.

Less than a second here. Yes, I can see it paint, but it's nowhere near 5 seconds. And I'm on a base model Thinkpad T440, hardly a speed machine these days.

Did you wait until the box was fully populated?

Yes.

Re: Firefox 57.0 Released

#765
post #130
post #90

Earlier quoted context omitted.

When you click on a new link, there is an "explosion" animation on the tab where it turns entirely blue for a second. This happens every time you click a link. I'm finding this extremely distracting. I'm sensitive to this kind of stuff so I always try to disable animations on everything I can. The top bar is also black-ish now rather than the system grey. This looks particularly bad with the new "blue" highlight indi…

FWIW, the tab shows the loading progress in blue, so you're seeing the result of quick page loads. Not arguing your experience, just clarifying what is happening. You might like the "Light" theme, which I think is available by default. That won't do any rounding for you, however.

No, it's actually a "this page has finished loading" animation. Personally I like it, but of course taste varies.

Re: Firefox 57.0 Released

#766

Earlier quoted context omitted.

Do you have any specific examples?

> Do you have any specific examples? Labels of background tabs became very transparent. This makes them completely unreadable, as my desktop background is quite dark. So, these tab labels are written with black letters on a dark blue background. So freaking good usability! /s

Switch to the "light" theme in the customization options. It looks better.

Re: Firefox 57.0 Released

#767
post #238

Earlier quoted context omitted.

> Note that the webextension APIs are still under active development. In which case, switching to webextension support exclusively is premature at this point, don't you think? It would have been better to wait until the API was robust enough to allow 99.99% of legacy extensions to be ported.

Unfortunately, this would have meant no Firefox Quantum. As a Firefox dev (I'm still working at Mozilla, although not much on Firefox atm), I have seen many, many occurrences in which I couldn't optimize codepaths, or even in some case fix bugs, because the old extension mechanism made it impossible. Consider the necessary steps: 1. realize that an internal API is broken; 2. come up with a new non-broken API; 3. port…

I know it's not really the subject, but since you work at Firefox: Is Thunderbird still actively developed? Or basically on life support?

Re: Firefox 57.0 Released

#768
post #756

Earlier quoted context omitted.

> Ah, well, sure, in that case, randomly breaking add-ons all the time would indeed have made our life easier. But everybody else's life would have been much worse, so we decided not to do that :) This is the part that I think you are going to get the most flak for. People are willing to deal with temporary setbacks if the changes can be brought in at some point. Permanently breaking things and calling that better wi…

> 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 PERMANENTLY break plugins with no way to ever fix them

Put another way: things were taking too long because of Mozilla's own self-imposed guidelines so the Firefox team had no choice but to PERMANENTLY break addons that will never be fixable by design because the Firefox team was so concerned about temporarily breaking plugins. This is double speak. The predicate (3) contradicts the subject (1).

After it was pointed out how ludicrous this sound the caveat is added that this had to be done in the name of security, performance, and privacy. At what point did security and performance become more important than an open platform and why? Numerous addons exist solely to provide privacy by blocking fingerprinting, stopping redirects, providing control over cross-site requests (RequestPolicy Continued), super-cookie safeguards (BetterPrivacy), and these options are no longer available. How are these privacy enhancing features being added now that the option has been removed since the goal is privacy?

The whole thing is hard to take at face value when everything seems to be self-contradicting (sans performance).

Re: Firefox 57.0 Released

#769

I just updated - WOW! What an improvement! Compared startup time and scrolling around some over-monetized sites; Behaves just as well as Chrome. Time for a switch again, I've missed FireFox since I started having Chrome as my default browser back in ~2011

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 updated versions out. Namely, Video DownloadHelper and Greasemonkey, both extensions I thought would die with Firefox 57 out. That said, I wouldn't have known if I hadn't looked at the add-ons site as near as I can tell, while they still say "Legacy" in my Add-ons tab, they do have separate releases on the add-ons site specifically for Firefox 57 which are incompatible with my current browser and I'll probably have to install them again when I do update.* Assuming that is the case, you might find a decent chunk of that 70% already ready and you just have to take some extra steps to get them working again.

Overall, I am optimistic, lots of people have lots of nice things to say about 57 and the extensions situation is not looking nearly the sort of bad I was first expecting. I'm sure I've had more painful wait periods for my extensions going back almost a decade ago as it seems I really am waiting on just one and that one is coming shortly. Even those extensions which are now unsupported actually seem to have decent replacements and I've switched them over already.

* Note, this portion is entirely speculative, refer back to my commentary on waiting till an updated NoScript comes out before I actually install Firefox 57. It's possible they would just update once I do upgrade to 57 rendering my subsequent speculation entirely wrong.

Re: Firefox 57.0 Released

#770
post #529

Earlier quoted context omitted.

https://duck.co/help/company/advertising-and-affiliates

My point is that "they're not an ad agency" is not an argument that a company has some incentive to protect user privacy, and "they're an ad agency" is not an argument that a company is incentivized to sell user data.

What does incentivise them is that their entire marketing is based around the privacy messaging, and thus pretty much their entire userbase considers that their primary selling point. If it ever came out that they were handing over that data to whomever, they'd be gone in an instant.
Post reply on HN