Status: Untriaged Owner: pkast...@chromium.org Labels: Type-Bug Pri-3 OS-All Area-BrowserUI
New issue 6038 by pkast...@chromium.org: Bounds computed incorrectly for dragged tab http://code.google.com/p/chromium/issues/detail?id=6038 While dragging a tab within the tabstrip, its bounds are computed as being in whatever "slot" of the tabstrip we think it corresponds to. This can cause problems when we HitTest() while dragging, e.g. to determine if we should close the tab on a middle click; we use the "tab slot bounds" instead of the bounds corresponding to the visible tab graphic, leading to slight weirdness. It would be nice (IMO) if we could also do something about the gap between the tabs and the New Tab button in the case when the dragged tab is considered to be at the end of the strip, since this has always looked weird to me. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
