[kijin]

Why can't we have the best of both worlds?

If the user clicks on the topmost pixel and immediately releases the button, they're probably trying to click on a tab. If the user moves the mouse while holding the button, they're probably trying to drag the whole window.

jQuery UI allows me to make things both clickable and draggable, and it always understands which of the two actions I'm trying to perform. There's no reason why a native app shouldn't be able to implement a similar feature.

[regularfry]

If they move the mouse while holding the button, how do you tell the difference between trying to move the window, and trying to move just that one tab?

[kijin]

When you're trying to reorder tabs, you are much more likely to click on the tab itself, not the pixel above it. Try it yourself, it happens naturally. Drag-and-drop usually involves more precise mouse control than simple clicking.

So the software can safely assume that if you drag the top pixel, you're trying to move the window rather than the tab.

[TeMPOraL]

> Why can't we have the best of both worlds?

Because then the UI will be confusing - the same place and action (clicking in the top) will affect either application or window manager. Also, sometimes you want to drag tabs around to e.g. reorder them or move to a new window.

[kijin]

Clicking != dragging. Same place, different action. Just because dragging starts by clicking doesn't mean that the computer should react in the same way. Double-clicking also starts by clicking, but most computers are perfectly capable of reacting differently to a double-click.

Switching to a tab upon clicking the top pixel is also perfectly consistent with what usually happens when you click on the chrome of any window:

1) Clicking on the title bar (top pixel) = Switch to window, and activate the element at pointer location, which in this case is a tab. Try clicking on the "Minimize" button of any background window to see this paradigm in action. The window is brought to the foreground and immediately minimized.

2) Clicking on an actual tab = Switch to tab.

3) Dragging on the title bar (top pixel) = Drag the window.

4) Dragging on an actual tab = Drag the tab.

[anon4]

Funny you should mention double-clicking

5) double clicking the tab bar = New tab

6) double clicking the title bar = Maximize/Restore

And then you double-click the titlebar instead of the tabbar by mistake and your window jumps away.

Or just have a stupid option and let the user decide. Maybe have that context-sensitive behaviour as default, but let me say that I want the title bar to be the title bar and tab bar to be the tab bar and have the two not mix together.

[kijin]

> 5) double clicking the tab bar = New tab

Does Opera really do this? Firefox and Chrome don't, and for good reasons, I think.

[reubenmorais]

Firefox does this, on OS X at least.

[ubercow13]

But 1) and 3) don't make sense together. In 1) you are apparently clicking a tab but in 3) if you drag the same pixel, it's no longer a tab.

[kijin]

If you click, it's a tab. If you drag, it's a window. What's so difficult about that? There's no reason to click on a window that is already fullscreen, anyway. (OP's problem only occurs if the browser is fullscreen.)