Live data from Hacker News

Firefox 57.0 Released

mozilla.org

461–470 of 836 posts

Re: Firefox 57.0 Released

#461

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

Firefox is pretty similar looking as Chrome now. I liked FF before cause it looked different, now everyone just copies Chrome look.

While there are some similarities in the UI I don't think the photon design system is a chrome ripoff. http://design.firefox.com/photon/welcome.html

Re: Firefox 57.0 Released

#462

Earlier quoted context omitted.

To see tree style tabs updated so early is a so important to me. I've even got the non-technical SO on tree style tabs, they consider the browser broken if the add-on isn't working.

I don't see how to disable yhe existing horizontal tab bar though? Now I have both that and tree style :/

You'll need a custom userChrome.css

    @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");

    /* to hide the native tabs */
    #TabsToolbar {
        visibility: collapse;
    }
    
    /* to hide the sidebar header */
    #sidebar-header {
        visibility: collapse;
    }
You probably want to enable the menu bar if you do this, to stop the minimize/maximize/close buttons from overlapping the menu & other buttons on the right top corner.

Re: Firefox 57.0 Released

#463

Earlier quoted context omitted.

> electrovim is in no way a replacement for Vimperator. It's a couple of keyboard shortcuts. None of the current vim-like plugins for FF57 match what vimperator/pentadactyl can do. Uh, yes, I'm the author of Electrovim, so I'm quite aware of the functionality that I was literally unable to implement because no equivalent API existed. > The problem I have isn't that they broke legacy things, it's that they broke legac…

Is it impossible to support window or otherwise chrome-level event listeners and also e10s? As I said in a prior comment, there seems no a priori reason that should be the case.

> Is it impossible to support window or otherwise chrome-level event listeners and also e10s?

Yes, because those things are now running in different processes, which means it requires IPC, and allowing extensions to communicate over IPC with the chome throws all the benefits of e10s out the window.

Re: Firefox 57.0 Released

#464
It's great, until you go to stream a video. Then the fans kick on, the computer gets too hot to hold... Been this way forever, hope Firefox can address this at some point in a future release.

Re: Firefox 57.0 Released

#465
Forgetting about the speed for a moment (which is great), I like the direction they are taking the user interface. Recent versions of FireFox had terribly clunky and frustratingly bizarre UI elements, 57 is a huge improvement.

Re: Firefox 57.0 Released

#466

I too am sad that despite the awesome speed, I'm forced to stick with v56 out of necessity for my add-ons. Tab Groups (which was originally a first-class Mozilla feature called Panorama) absolutely changed my browser workflow, and I can't imagine regressing... The new APIs won't support replacement any time soon, and the dev has already given up, since they'd already had to run a fundraiser once to add Electrolysis s…

Try Tree-Style Tabs. It totally replaced tab groups for me, it's far more capable.

Re: Firefox 57.0 Released

#467

Earlier quoted context omitted.

Tried this. It was too complicated and slow enabling every subdomain by hand.

The granularity is up to each user, none is enforced. I personally just stick to base domains usually. When a site is broken, allowing one or two 3rd-party base domains is often just enough to fix it. If you want to go subdomain-granularity, this is your choice -- it's not forced on you. Some even go as far as subdomain/type (the cells in the middle).

I think the bigger problem is that it exposes the grid from the word go.

I myself though i had to enable each sub-set individually until i took a closer look at the behavior when clicking certain ui elements (that as i recall were unlabeled).

Noscript on the other hand only present a list of domains, though one can enable sub-domain granularity in the options (never felt the need).

Re: Firefox 57.0 Released

#468

I too am sad that despite the awesome speed, I'm forced to stick with v56 out of necessity for my add-ons. Tab Groups (which was originally a first-class Mozilla feature called Panorama) absolutely changed my browser workflow, and I can't imagine regressing... The new APIs won't support replacement any time soon, and the dev has already given up, since they'd already had to run a fundraiser once to add Electrolysis s…

WebExtensions were specifically announced alongside Electrolysis. This is not Mozilla's fault.

Re: Firefox 57.0 Released

#469

Earlier quoted context omitted.

To see tree style tabs updated so early is a so important to me. I've even got the non-technical SO on tree style tabs, they consider the browser broken if the add-on isn't working.

I don't see how to disable yhe existing horizontal tab bar though? Now I have both that and tree style :/

There is no OOB way to do it ATM, you need to modify the userChrome.css. see below for more details.

https://www.reddit.com/r/firefox/comments/736cji/how_to_hide...

Post reply on HN