Live data from Hacker News

Firefox 25 will get a major UI overhaul

wiki.mozilla.org

181–190 of 194 posts

Re: Firefox 25 will get a major UI overhaul

#183
post #112
post #68

Earlier quoted context omitted.

I think Firefox should switch to Qt, since it allows more flexible management. For example GTK prevents it from drawing in the title bar.

That's called client side window drawing and GTK has it. Needed for Wayland. Maybe good to investigate a little bit before saying things that aren't true.

Also, I'm not sure how Wayland is going to solve that, since Wayland protocol doesn't mandate for the window manager to use client side decorations. May be you are talking about Weston (which is a reference compositor of the Wayland project). But in practice each major DE will probably create their own compositors which won't necessarily use client side decorations.

Re: Firefox 25 will get a major UI overhaul

#184

Yet after Lion, Mountain Lion, and in a few month the new Mac OS, they still haven't implemented the native scrollbar and bounce scrolling... Mozilla is doing a lot of stuff, but I don't see any focus.

Yeah, how dare Mozilla not instantly implement the constant stream of random UI modifications Apple makes on a whim that require every developer to overhaul their UI and potentially make the UX worse? From my perspective, not making that nonsense priority #1 demonstrates Mozilla's focus on features that actually matter. Also, patches welcome, write an extension, etc etc etc.

"Instantly" was true when Lion launched. It's been ages now. And the new design clearly is not "focus on features", but UX. Regarding patches, their have been patches for the scrollbar since day one. It's just Mozilla bureaucracy that makes it impossible to land.

Re: Firefox 25 will get a major UI overhaul

#185
post #159
post #136

Earlier quoted context omitted.

The fullscreen API works fine. A website can display itself without any other clutter on the screen (with user permission). Unfortunately, it is no longer possible for a user on Mac OS X to cause the switch to fullscreen. The view menu (Firefox 21.0, for example, on OS X) still offers an "Enter Full Screen" menu item. Unfortunately, all it does is hide some of the chrome (it hides the menu bar and the title bar), lea…

I just tried this on Nightly and the chrome that's left behind (tabs + URL) slide up and out of the way within half a second of entering full screen mode, leaving nothing but the webpage on the screen. Are you sure that this isn't happening for you?

Works great on Linux, but that feature is totally absent on OS X.

I'm using this add-on in the meantime, but it has other issues: https://addons.mozilla.org/en-US/firefox/addon/old-lion-full...

Re: Firefox 25 will get a major UI overhaul

#186
post #150
post #123

Earlier quoted context omitted.

Those tabs look nice when you have 3 or 4 of them. But I have 26, and it won't look so good then. (I tweaked my chrome to shrink the minimum tab size, so I can get lots of them without having to scroll the tab bar.)

Try Tree Style Tab, it displays tabs on the left. It's a bliss.

I tried it about a year or 2 ago and my browsers wouldn't stop crashing. It also had a memory leak.

Maybe it's better now and I should try again.

Re: Firefox 25 will get a major UI overhaul

#187
post #182

Redesign away, as long as pentadactyl keeps working.

Thae addons page says that pentadactyl does not work on FF 21. What is the deal with that? https://addons.mozilla.org/en-US/firefox/addon/pentadactyl/

The addons page hasn't been updated for a while. The nightly works fine on version 19.0.2. Haven't tried with version 21 though.

Re: Firefox 25 will get a major UI overhaul

#188
post #159
post #136

Earlier quoted context omitted.

The fullscreen API works fine. A website can display itself without any other clutter on the screen (with user permission). Unfortunately, it is no longer possible for a user on Mac OS X to cause the switch to fullscreen. The view menu (Firefox 21.0, for example, on OS X) still offers an "Enter Full Screen" menu item. Unfortunately, all it does is hide some of the chrome (it hides the menu bar and the title bar), lea…

I just tried this on Nightly and the chrome that's left behind (tabs + URL) slide up and out of the way within half a second of entering full screen mode, leaving nothing but the webpage on the screen. Are you sure that this isn't happening for you?

Yes, I'm quite sure. On OS X, I can get real full screen with Chrome, and I can get it with Firefox if the website itself initiates it. But the "full screen" in the View menu removes half of the chrome and leaves the other half. Useless.

It turns out I'm not the only one complaining. It has been a known issue since at least early 2012. Apparently, some of us think full screen should mean FULL screen. Nobody at Mozilla is working on it: https://bugzilla.mozilla.org/show_bug.cgi?id=740148

Re: Firefox 25 will get a major UI overhaul

#189
post #64

Earlier quoted context omitted.

1. I don't believe Firefox UI is busy 2. We always had those kind of "busy" UI since IE, Netscape, Opera and Firefox. 3. Chrome comes around, makes a very simplistic UI and now many people assume that it's the only way. IMO Chrome is just too simplistic, It's beautiful yes but is it efficient? For example, the first thing I do when I install Firefox on a machine is to display the menu bar. And I think it's a shame th…

>it's a shame there is no more status bar as well https://addons.mozilla.org/en-US/firefox/addon/status-4-evar...

Thanks, just installed it, working wonders!

Re: Firefox 25 will get a major UI overhaul

#190
post #53

Earlier quoted context omitted.

The inconsistency is based around a scenario like this. Open 4 tabs. click tab 1 and then tab 3. What order do you display the tabs in? Does tab 1 overlay tab 2? If closing tabs don't to the last open tab this now means that the visual stack is not accurate to how the program operates. I understand the depth but there are better ways to show it that don't take up as much space nor have to deal with issues like visual…

Chrome stacks away from the currently focused tab. If tab 6 of 10 is focused, 6 will be in front of 7, which is in front of 8, and so on; similarly 6 is in front of 5 which is in front 4, and so on. There is a subtle visual lead to the focused tab. If you then select tab 2 for example, tabs 3 to 6 will be restacked for consistency.

I loathe that behaviour, it was one of the things that bugged me about Chrome. If I close a tab, I want the focus to go back to the previously viewed tab, not the previous tab in the z-stack.
Post reply on HN