Changes

Jump to: navigation, search

Ctrl W not close app

1,296 bytes added, 19:08, 5 December 2007
Behavior dependent on tab bar visibility: I think not a good idea -- it is trying to link two unrelated options that should be independently configurable.
* The difference between pseudo-MDI- and pseudo-SDI-mode isn't always obvious
* You'll need an extension if you want to break this logical tie
 
----
::Comment:
:::It appears that this suggestion has now already been implemented, '''but...''' I'm not convinced that the reasoning is sound. Just because you choose to not hide the tab bar with only one tab left, it doesn't mean that you necessarily thinking in terms of Firefox as "tabbed browsing shell". Personally I think far more in terms of the "document viewer" model, but still choose not to hide the tab bar for entirely other reasons. So there really are two separate options that the user should be able to select independently.
 
:::To illustrate this, I will describe my own reasons for not hiding the tab bar, although this is probably just one example, and others may have other reasons. I have enabled the option to open tabs in the background, and I therefore reasonably expect that if I click to open a page in a new tab, that it will do so in a way which is minimally disruptive to my reading the current page. But if I hide the tab bar when there is only the one tab, then when I open the second tab, the text on the current page will all shift downwards in order to make space for the tab bar to appear. Because this behavior is disruptive to reading the current page, I instead always show the tab bar.
 
:::[[User:Alan I|Alan I]] 11:08, 5 December 2007 (PST)
----
==Question==
1
edit

Navigation menu