I don't agree. I think the pull-off sensitivity is calibrated perfectly... Unless, for some strange reason, the behaviour that I see is different from yours. Anyway, I can say that I have NEVER pulled off a tab by mistake when I was simply clicking on them. And I've been using Chrome since it was released. You are not the first to complain about this, though, so maybe there are really some differences between my version and yours - due to what, it's anybody's guess....
On 20 Mar, 19:24, Luis LDQ <[email protected]> wrote: > Immediately after I switched to the Dev channel earlier this week, I > found myself pulling off tabs when I meant to switch to them by > clicking them. > > IMHO, this is how it should work: > > PULL OFF: > while mouse button is held after clicking a tab: > if there is vertical movement beyond the top and bottom of the tab > greater than 50% of the height of the tab: > if the mouse button is held for longer than two seconds AFTER > they've moved more than 50% of the height of the tab away > pull off tab > else keep tab in place > else keep tab in place > > REARRANGE: > It seems to me that it currently works like this: > > if a tab being dragged horizontally occludes >= 50% of an adjacent > tab: > swap the tabs > > I propose this threshold be raised to >= 75% of an adjacent tab. > Cf. Issue 9075:http://code.google.com/p/chromium/issues/detail?id=9075 --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
