Live data from Hacker News

The future Firefox UI

people.mozilla.com

161–170 of 191 posts

Re: The future Firefox UI

#161

Earlier quoted context omitted.

I'm not sure what you're referring to. On my computer, it looks either like [this]( http://i.imgur.com/jZiFO.png ) or [this]( http://i.imgur.com/yHMKH.png ). No "floating button in the top left" either way.

http://i.imgur.com/d4jjL.png

That can't be it, he said, "it's on its own line with the tabs showing up below it".

Re: The future Firefox UI

#162
post #159

Earlier quoted context omitted.

> or the whole menu bar disappearing when you use an extension in its own window Could someone explain to me the correct way for a developer to handle this? I've been aware of this problem for a while, and I've newly come to own a Mac, so I've looked into it more and looked at what other apps are doing. There doesn't seem to be a correct solution. I looked at how Safari handles the Web Inspector, and it just adds a n…

I think the solution that Apple would suggest is to just not put an "app-within-an-app". If the feature set is far enough apart that it feels like a separate app that needs a separate menu bar, it should be a separate app. (I actually agree: when is that ever better than a dedicated app?)

>when is that ever better than a dedicated app?

Obviously when it integrates well with a web browser. :P

Re: The future Firefox UI

#163
post #89
post #8

Earlier quoted context omitted.

What would you want to see in another browser that would make it worth switching away from chrome?

The shortlist would be: speed, standards compliance, UI, and developer support (I love that Chrome has built-in dev tools -- I know firebug exists, but compared to CDTs, again, it seems clunky).

Oddly enough, Gecko is usually more standards-compliant than WebKit. For example, it passes much more of the CSS 2.1 test suite....

People seem to not realize this, for some reason.

Re: The future Firefox UI

#164
post #124

Earlier quoted context omitted.

Ugh. I hate shapeshifting UIs. Muscle memory depends on stuff being fixed in space relative to other elements.

muscle memory is less relevant when mousing. the range of starting positions is large.

I can usually mouse to within a few dozen pixels of my target without looking at the screen, thanks to a combination of muscle memory and spatial sense.

Re: The future Firefox UI

#165
post #102

Earlier quoted context omitted.

I haven't used Lion yet, but from what I've seen, it's still far more consistent than Windows.

This is undoubtedly true (with the flagrant exception of iCal and Address Book), but some of us old-timey Mac users remember a glorious past full of matte gray and a spatial Finder…

Possibly the UI of iCal and Address Book might have the inconsistant UI, but they still have the exact same UX as every other OS X app, thanks to all (with the exception of iTunes?) being built in Cocoa so they all use the same text controls and menu items etc.

You can create a Cocoa app in XCode and just add a text field, and you will automatically get spell check, dictionary look-up and font controls. All your shortcuts will work exactly how you would expect them to (ctrl+a, I'm looking at you). You get a help menu with built in search of the menu bar (http://cl.ly/8yKI). All with no effort from the dev at all.

The only exception to this would be Adobe apps, but at least they have their own UI/UX that they seems to follow most of the time (but they actually hate Apple/OS X, so they probably just do it out of spite)

Re: The future Firefox UI

#166
I don't care as long as I can still use the Add-Ons (extensions, themes, etc.) to make it work like I want, which is pretty much like an improved Firefox 3.6 or so. That's the big thing Chrome doesn't have: The ability to customize the experience in very deep ways.

Re: The future Firefox UI

#168
They sure love showing off screenshots on Mac OS X. But when are they going to follow the basic Mac OS X convention of putting the close button on the left, and centering the tab titles?

Re: The future Firefox UI

#169
post #65

Does anyone know if they are planning on bringing back Ubiquity. Of the different lab projects, this one I miss a lot.

You can actually download[1] an updated version of Ubiquity that works with even the nightly versions. The commands I personally wrote seem to be broken now, but I think the main pre-installed ones work. [1] Get tip.xpi at https://bitbucket.org/satyr/ubiquity/downloads

Thank you so much for posting this. I have missed Ubiquity.

Re: The future Firefox UI

#170

Earlier quoted context omitted.

http://i.imgur.com/d4jjL.png

That can't be it, he said, "it's on its own line with the tabs showing up below it".

nxn messed up his or her pronouns. The "it" in "its own line with the tabs showing up below it" refers to the the title bar. It's that on Windows, the tabs and button take the place of the traditional title bar. On Linux, drawing in the title bar proved too difficult for a generalized approach that worked across window managers, so the title bar remains intact, and everything is offset by it.
Post reply on HN