[carussell]

> 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.

[Xuzz]

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?)

[carussell]

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

[starwed]

>when is that ever better than a dedicated app?

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