News for hackers. Stuff that matters.
Re:The future Firefox UI by jgranby on Monday August 01, 2011 @01:00PM (#2833212)
I wonder whether this latest proposed redesign will finally have Firefox behaving like, y'know, a native OS X app, or whether it'll be just as shallow as all previous efforts.
Re:The future Firefox UI by starwed on Monday August 01, 2011 @01:22PM (#2833324)
Curious, since I only recently started using a mac. How does firefox not act like a native app?
Re:The future Firefox UI by jgranby on Monday August 01, 2011 @01:34PM (#2833394)
The whole app feels like an imitation of a Mac app. Most obviously on 10.7, the window chrome is wrong. Other small things like incorrect and wrongly sized fonts inside controls, or the whole menu bar disappearing when you use an extension in its own window. When you add everything together, it just feels wrong, like wearing clothes that don't fit.

The way they've been updating the UI so far has seen some improvements, for sure, but it's as if they've been patching it bit by bit. I just wondered whether this signalled a change of approach.

Re:The future Firefox UI by carussell on Monday August 01, 2011 @07:54PM (#2835063)
> 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 new, dedicated Debug menu to the menu bar. This is a no-go in my case.

Suppose you're developer faced with a problem similar to the Firefox–extension problem. You have something like an app-within-an-app, or maybe A and B are actually even more closely tied together than that, but independent enough that on any other platform it would be a no-brainer: each one gets its own menu. What do you do for OS X?

You can't re-use A's menu items in B, because A's items—in, say, the Edit menu—don't serve B. You can't just augment A's menu set to include B's menus and items, because B's menus and items are so numerous and specific to B and vice versa, that there's just so much clutter from the other's menus and items.

Re:The future Firefox UI by Xuzz on Monday August 01, 2011 @09:53PM (#2835367)
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?)

Re:The future Firefox UI by carussell on Tuesday August 02, 2011 @03:32AM (#2836219)
I'll reply by pointing out that I wrote

> something like an app-within-an-app, or maybe A and B are actually even more closely tied together than that

Re:The future Firefox UI by starwed on Monday August 01, 2011 @11:28PM (#2835621)
>when is that ever better than a dedicated app?

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

Re:The future Firefox UI by sirn on Monday August 01, 2011 @01:37PM (#2833404)
Emacs keys binding not working in some place (e.g. Ctrl+N, Ctrl+P not working on Awesome Bar). Missing contextual services menu when you right click on some text. Missing text services (e.g. Cmd+Shift+D popup dictionary), etc. etc.
Re:The future Firefox UI by ryanpetrich on Monday August 01, 2011 @01:38PM (#2833407)
All of the Cocoa UI controls are reimplemented in XUL. They look and behave close to, but not 100% the same as the native Cocoa ones.
Re:The future Firefox UI by ZoFreX on Tuesday August 02, 2011 @07:54AM (#2836786)
I have to use a Mac at work and frankly none of the programs I use feel like Mac apps. Everything in the Adobe suite is the same as on Windows except slower (down to the 8 corner resizing), Firefox is as you say, and I have to agree with the statement I saw earlier today that Eclipse is a cross-platform Windows application.

Interestingly I have the exact same issue with Firefox on Android. The address bar isn't a native text box, it's fake! I have two non-standard things happening on text boxes, Samsung's cursor indicator and the Swype keyboard, and nothing behaves quite as it should.

Are developers giving up on using native widgets?