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

Firefox 50.0

mozilla.org

Post reply on HN
Print view View original

51–60 of 205 posts

Re: Firefox 50.0

#51

Post by Manishearth »

kuschku wrote: post #30
Manishearth wrote: post #16

Earlier quoted context omitted.

> Granted, it's done by mimicking Webkit APIs, That's ... not a bad thing. Chrome creating nonstandard APIs (IIRC this was for Drive?) on its own is a bad thing. Coming together and speccing ( https://wicg.github.io/directory-upload/proposal.html ) the API is a good thing. They seem to have specced more or less what Webkit had already implemented (plus some promise based stuff), but usually when a nonstandard API has…

> They seem to have specced more or less what Webkit had already implemented The problem is that the WHATWG always just standardizes "whatever Chrome does". This leads to the HTML living standard actually being just like Office Open XML, with one entity controlling all of it.

> WHATWG always just standardizes "whatever Chrome does".

It really ... doesn't. When the situation has arisen that Chrome has implemented an API for long enough for it to become entrenched in the web, it then discusses standardizing it (see also: https://compat.spec.whatwg.org/). But it's not blindly following Chrome, it's only in these special cases.

I've recently been involved in a couple of issues where browsers disagree with each other and/or the spec. Each time there's a discussion, and the best version of the behavior is chosen and worked into the spec. This best version is not always the Chrome version.

Re: Firefox 50.0

#53

Post by criddell »

I wanted to try reader mode, so I went to a random Atlantic article (https://www.theatlantic.com/health/archive/2016/11/better-of...) and hit ctrl-alt-r. The graph related to the story was dropped. Would that be a bug, or is that how reader mode is supposed to work?

I don't have the equivalent Evernote plug-in anymore (I'm trying to get away from Evernote), so I have nothing to compare it to.

Re: Firefox 50.0

#55

Post by kylek »

spacehacker wrote: post #14

Obligatory "does it break Tree Style Tabs?" comment.

You might want to check out Test Pilot and the Tab Center addon : https://testpilot.firefox.com/experiments/tab-center

Unfortunately it is very slow compared to Tree Style Tabs if you have a considerable amount of tabs open (even using extensions like auto-unload, it is very very slow). Hope it gets fixed because I would _love_ a built-in vertical tab feature.

Re: Firefox 50.0

#56

Post by ohstopitu »

Aardwolf wrote: post #24

"Set a preference to have Ctrl+Tab cycle through tabs in recently used order " Finally something that is an actually improved UI feature! Not some "removed status bar and instead hover its info over text you want to read sometimes" or "moved refresh button to different place than before just to annoy you" or similar thing :)

I have this feature in sublime text & Atom and absolutely hate it.

I feel like ctrl + tab has to move to next tab & ctrl + shift + tab should move to previous tab (cycle if it reaches the end).

I feel like that's more predictable behaviour.

Re: Firefox 50.0

#57

Post by abusque »

ohstopitu wrote: post #56
Aardwolf wrote: post #24

"Set a preference to have Ctrl+Tab cycle through tabs in recently used order " Finally something that is an actually improved UI feature! Not some "removed status bar and instead hover its info over text you want to read sometimes" or "moved refresh button to different place than before just to annoy you" or similar thing :)

I have this feature in sublime text & Atom and absolutely hate it. I feel like ctrl + tab has to move to next tab & ctrl + shift + tab should move to previous tab (cycle if it reaches the end). I feel like that's more predictable behaviour.

I don't know about Firefox or Atom, but in Chromium you can achieve that via Ctrl-PgUp and Ctrl-PgDn.

Re: Firefox 50.0

#58

Post by Washuu »

dbl9 wrote: post #34
Aardwolf wrote: post #24

"Set a preference to have Ctrl+Tab cycle through tabs in recently used order " Finally something that is an actually improved UI feature! Not some "removed status bar and instead hover its info over text you want to read sometimes" or "moved refresh button to different place than before just to annoy you" or similar thing :)

I'm glad you like it. This is one of those personal UX preferences that has you either one or the other camp. Am I right to assume you liked this from your past Opera use?

I was excited to sudden see this surprise in the patch notes, now I am the opposite here thinking, "How did they mess up such a simple feature?" The preview bar that pop ups is slow to work and actively delays changing tabs.(If it even attempts to switches tabs.) Additionally, I do not need the preview portion.

FLST: https://addons.mozilla.org/en-US/firefox/addon/fww-flst/

It just works. Tab switching is instant, no unnecessary preview, and it has never messed up remembering tab order.

Re: Firefox 50.0

#59

Post by dbl9 »

kbenson wrote: post #45
dbl9 wrote: post #26

Earlier quoted context omitted.

For the same reason they haven't made 64-bit the default on Windows and provide two versions. There are many users for whom only one variant works reliably. If upstream, like in the case of cairo-gtk3, decides GTK2 is not supported anymore, it's a matter of chance whether your cairo-gtk2 build of Firefox works at all. For instance, for me 49.0.2 gtk2 local build on Arch crashes anytime I try to use the file dialog, w…

On windows, Firefox is the main supplier of binaries. I would hazard that on most Linux/BSD systems, the distribution is the main supplier of binaries. The distributions can easily build it as GTK2 if they want, or provide a GTK2 variant (and as pointed out above, some distributions seem to, or at least make it easy to build it yourself). If you are on Linux and your distribution provides Firefox, this is a complaint…

In the past the GTK3 code path was tested only by Red Hat as the primary developer of all things GTK and GNOME. At that time, there was only a GTK2 build from Mozilla, and now instead of doing the same as Windows 32-bit/64-bit we're presented with just GTK3 support with the promise to obsolete the GTK2 code, while seemingly not considering the regressions of GTK3.

Why do we use Mozilla binaries of Firefox on linux distro where there's Firefox builds in the package repository? Many reasons:

1. fast access to security fixes

2. access to EMEfree builds

3. access to different channels

While it is easy to build with cairo-gtk2 as the backend, that code path, as I wrote in a sibling comment, reliably crashes for me anytime I try to do File-Open. I'll try to find out if that AUR recipe or Gentoo ebuild do something different that makes it stable, but the fact remains that GTK2 is about to be unsupported by Mozilla while GTK3 hasn't gotten stable yet, which will make life for anyone that tries to build a GTK2 variant very hard. Therefore, I wouldn't really say it's an easy choice.

Re: Firefox 50.0

#60

Post by acqq »

Still relatively slow startup, even on my quite powerful computer (i7, SSD, 8GB RAM, the second start, everything already cached in RAM, no add-ons or extensions but the defaults, no sessions restored, open to empty tab) I have at least a whole second during which I don't see that the program is starting.

At least visibly better than the 49.

Post reply on HN