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

Firefox 57.0 Released

mozilla.org

Post reply on HN
Print view View original

241–250 of 836 posts

Re: Firefox 57.0 Released

#241

Post by urlwolf »

barrkel wrote: post #7

Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…

Argh, it dropped one feature that I loved: clicking on current tab does a ctrl tab.

Re: Firefox 57.0 Released

#242

Post by Yoric »

Tomte wrote: post #128
iterati wrote: post #98

Earlier quoted context omitted.

The right thing to do would have been to work on those extensions BEFORE breaking users' experience.

Mozilla doesn't create all those extensions. And the extensions' authors had, what, two years advance warning or so? Criticize the real culpits, not Mozilla.

As a Mozilla dev, I fully support the move to WebExtensions, but I also disagree with you.

Porting an add-on to a whole new architecture is lots of work. People who do this on their spare time, or small companies, or companies relying on contractors, may not have the time/resources/will to do it, even within two years. Also, in some case, the APIs are simply not available.

As for why I believe that the move to WebExtensions was necessary and could not be postponed further, I have written a few lines in another thread: https://news.ycombinator.com/item?id=15695854

Re: Firefox 57.0 Released

#243

Post by TheRealPomax »

andrepd wrote: post #51
barrkel wrote: post #7

Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…

The WebEx Tree Style Tabs is markedly inferior to the "Legacy" version. It is simply an integral and indispensable part of my workflow, so much that I can't even fathom browsing without it. I guess I'll stay on 56 for a while.

Sooooo did you make a donation to the author so that they actually have a reason to spend some of their personal time on improving it beyond the initial porting effort? I mean, they have a life they need to live and time they need to allocate too, right? If it's and indispensable add-on, you can probably part with a few bucks to help get it improved to the level you need, rather than the level the author felt was appropriate.

Re: Firefox 57.0 Released

#244

Post by tmzt »

callahad wrote: post #220
frayesto wrote: post #110

Anyone else use PocketCasts web player? Chrome is able to play audio at 2.7x speed without distortion while Firefox still has issues. Is there a location where I can submit a bug report?

We track most of our bugs in Bugzilla ( https://bugzilla.mozilla.org ). Once you've created an account, go to File a Bug, Core, and choose "Audio/Video: Playback" as the Component in the form. (In general, it's fine to chuck bugs into Firefox -> Untriaged and they'll eventually land in the right place.) If Bugzilla's a bit of a pain, just let me know and I'll happily file it for you.

Are Quantum bugs in bugzilla or Github?

Re: Firefox 57.0 Released

#245

Post by oblio »

huhtenberg wrote: post #218

Is there a pre-57 theme for the UI? The new one is way too minimalist. It also appears to target people with poor sight all chrome elements suddenly became larger. EDIT - The upgrade also wiped all GreaseMonkey scripts for some reason. Hmm. EDIT - Downgraded back to 56. Way too many jarring UI changes as well as the AddOn breakage to justify the new snappiness. Mozilla also appears to have pulled the link to the "old…

You can reconfigure almost everything back...

For the chrome elements size: Menu -> Customize -> Density -> Compact.

Re: Firefox 57.0 Released

#246

Post by oblio »

DiThi wrote: post #227
oblio wrote: post #217

Earlier quoted context omitted.

On the other hand, for some reason they've decided to make the tab previews smaller. Now I have a bunch of small thumbnails on a huge page... And now way to increase their size :(

Have you tried Ctrl-wheel or Ctrl-+ (plus key)?

Huh, it's actually saved, I thought it was a temporary setting. Thanks! :)

Still not perfect, since I'm just zooming in some PNGs. And the new thumbnails are square while most pages that I view are rectangular. But it will do, for now.

Re: Firefox 57.0 Released

#247

Post by amaranth »

digi_owl wrote: post #108
iterati wrote: post #98

Earlier quoted context omitted.

The right thing to do would have been to work on those extensions BEFORE breaking users' experience.

Sadly not how the FOSS world works any longer. All that matters is the "shiny" (often wrapped in some kind of "social consciousness" claptrap), and those of us that has come to rely on existing behavior has to either suck it up, move on, or fork (And even forks struggle)...

I don't remember the FOSS world _ever_ working like you seem to think it should. The CADT Model[1] isn't exactly new and it wasn't really new when jwz coined the term either. Only the kernel, POSIX-y things, and enterprise software provides what you're asking for. And forks of Firefox struggle because writing a browser is really really hard and they can't keep up with the changes needed.

[1] https://www.jwz.org/doc/cadt.html

Re: Firefox 57.0 Released

#248

Post by wpietri »

Yoric wrote: post #238
doodpants wrote: post #180

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'm sure you'll hear a zillion complaints, but I really appreciate you folks doing this. I've been using a beta version for the last few months on one of my computers and it's so very much better. I can't wait to have it everywhere.

As long as you're here: I was told that the old extension API was way too broad, locking in a lot of design choices that were not really considered from the "do we want to maintain this for years and years" perspective. And that the new one is much more focused and considered. Is that the case?

Re: Firefox 57.0 Released

#249

Post by Yoric »

rvanmil wrote: post #154
awinder wrote: post #120

This is so close to great but can a mac snob ask how to get a more consistent UI experience out of firefox? I'm totally happy with how everything behaves inside the web panel but: 1. At a minimum I'd be happy with a toolbar icon set that was a little more in step with OS X design (but willing to hear if I just have misunderstanding of design :D) 2. As a reach, os-native menus or at least more native-style menus for t…

If only they'd put all the effort spent into trying to imitate macOS into actually building an AppKit version... I guess that's never going to happen due to the cross platform nature of Firefox, but it also means (among other reasons) I'll never use it as my primary browser.

There used to be a MacOS native Mozilla browser [1] called Camino. It was kind of killed by Safari, though.

[1] Or is it a "macOS native mozilla browser", these days? everything seems to lose its uppercase.

Re: Firefox 57.0 Released

#250

Post by zeveb »

barrkel wrote: post #7

Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…

> Hopefully most of the missing extensions will be developed sooner rather than later.

The API is still missing the ability to implement some things, which is preventing developers from supporting the latest Firefox.

I won't upgrade until Keysnail is able to run.

Post reply on HN