Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 1 user
Status: Fixed
Closed: Jul 2010
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: ----
Type: Bug

  • Only users with EditIssue permission may comment.

Sign in to add a comment
"Gap" in tabs while dragging is incorrect when windowing buttons are on the left
Reported by, Jul 10 2010 Back to list
Chrome Version (from the about:version page):
Google Chrome	6.0.458.1 (Official Build 51742) dev
WebKit	534.3
V8	2.2.22
User Agent	Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.458.1 Safari/534.3
Is this the most recent version: Yes
OS + version: Ubuntu 10.04
CPU architecture (32-bit / 64-bit): 32
Window manager: GNOME/Metacity
URLs (if relevant): n/a
Behavior in Linux Firefox: n/a
Behavior in Windows Chrome (if you have access to it): n/a

What steps will reproduce the problem?
1. Use chrome in gnome, where the close/minimize/window buttons are on the left.
2. Open a significant number of tabs. (More tabs make it easier to notice)
3. Drag tabs around to reorder them. (Tabs on the right end have a more dramatic effect)

What is the expected result?
The "gap" in tabs should be near to the location of the mouse.

What happens instead?
The gap is offset, making it more difficult to reorder tabs.
I assume the calculation assumes that the windowing buttons are on the right. So, when it goes to calculate the position of the gap, it is off by about 100px.

Please provide any additional information below. Attach a screenshot
and backtrace if possible.
(backtrace n/a)

Made a mistake; wrong screenshot.
Screenshot-New Issue - chromium - Project Hosting on Google Code - Google Chrome.png
102 KB View Download
Comment 2 by, Jul 14 2010
Labels: Mstone-6
Status: Started
Labels: -Area-Undefined Area-UI Feature-TabStrip
Comment 4 by, Jul 15 2010
The following revision refers to this bug: 

r52507 | | 2010-07-15 11:50:54 -0700 (Thu, 15 Jul 2010) | 8 lines
Changed paths:

[GTK] correct tabstrip drag point calculation.

Must account for discrepancy between widget->window coordinates and widget coordinates.

BUG= 48774 
TEST=see bug

Review URL:

Comment 5 by, Jul 15 2010
Status: Fixed
Project Member Comment 6 by, Oct 12 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 7 by, Mar 10 2013
Labels: -Area-UI -Mstone-6 -Feature-TabStrip Cr-UI-Browser-TabStrip M-6 Cr-UI
Project Member Comment 8 by, Mar 13 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Sign in to add a comment