Did something change in font rendering with Freetype on Linux? While 49.0.2 with FreeType 2.7 looked the best (subjectively) I've seen any font rendering (including Windows 10 and OS X Snow Leopard (been a while)), something off with 50.0's rendering. I haven't enabled any custom render options, just your typical archlinux freetype 2.7 desktop. Time to get ESR and compare with that but would be great to hear back from others with a similar environment.
Firefox 50.0
31–40 of 205 posts
Re: Firefox 50.0
#32Earlier quoted context omitted.
If it is that bloody simple, why can't Mozilla be bothered to provide an official download?!
Possibly for the same reason they don't ship Tk compiled versions. Why should they target every GUI toolkit and complicate their build process which they then have to deal with supporting? If it's that easy, you can probably find some third party that compiles and offers it. I'm not sure why you think Firefox needs to do it themselves.
I know you're being facetious, but Mozilla shipped Motif builds for a really long time after most of the world had switched to GTK. Far longer than seemed reasonable at the time. Given that the majority of GTK-running systems support GTK2, and that the GTK3 builds of Firefox require GTK2 already, it seems very strange that the default distribution would bother with GTK3 at this time. I'm sure they have good reasons; I'm just curious about what they are.
Re: Firefox 50.0
#33Breaks NoScript on launch day. That was an unpleasant surprise this morning...
I'm on the Aurora channel currently running 51.0 and NoScript works fine for me.
Re: Firefox 50.0
#34"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?
Re: Firefox 50.0
#35Earlier 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.
I would postulate that the cause of this is that, as a provider of services, Google kind of knows what's difficult to do in a browser and what apis are needed to make it more native-like.
So it's not a terribly bad thing, unless other people's standards are just being ignored
Re: Firefox 50.0
#36Earlier quoted context omitted.
Possibly for the same reason they don't ship Tk compiled versions. Why should they target every GUI toolkit and complicate their build process which they then have to deal with supporting? If it's that easy, you can probably find some third party that compiles and offers it. I'm not sure why you think Firefox needs to do it themselves.
I know you're being facetious, but Mozilla shipped Motif builds for a really long time after most of the world had switched to GTK. Far longer than seemed reasonable at the time. Given that the majority of GTK-running systems support GTK2, and that the GTK3 builds of Firefox require GTK2 already , it seems very strange that the default distribution would bother with GTK3 at this time. I'm sure they have good reasons;…
Do you know how to run Firefox 50 with GTK 3.22.0 and the native Wayland backend? If I try it, it crashes instantly, and I was surprised to see gtk3 and gtk2 linkage in the xul libs. Any idea?
Re: Firefox 50.0
#37"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?
Actually I like it from IDE's and text editors :)
As well as the alt+tab desktop behaviour
Re: Firefox 50.0
#38"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 :)
This has been possible for a very long time, as a side-effect of enabling browser.ctrlTab.previews in about:config
Glad to see they are paying more attention to this though.
Thousands of people have requested that feature for Chrome. To this day there hasn't been (or I haven't found) an official answer and the only way to do it is to use an extension, using an alternative keybind as extensions aren't allowed to interact with ctrl-tab.
Re: Firefox 50.0
#39Earlier quoted context omitted.
If you have a hard requirement to use a thoroughly obsolete GUI toolkit, you can for now fairly easily compile your own copy of Firefox for GTK2; it takes around 30-40 minutes on a laptop with a Core i5. (On Gentoo, there is a USE flag for it.)
If it is that bloody simple, why can't Mozilla be bothered to provide an official download?!
If there are a bunch of people that need this you could do the community a service by doing it and hosting it somewhere for all interested parties.
Re: Firefox 50.0
#40Any firefox devs here? You guys broke your own VTT polyfill with this update: https://github.com/mozilla/vtt.js/issues/354 Only reason I'm mentioning it here is that it looks like the repo is dead.
I'm making some inquiries. It looks like the old code just ended up setting "position" to 0 when an object was assigned, while the new code (correctly per spec) throws. The real bug is assigning an object to a non-object-valued property...