Closed Bug 666248 Opened 13 years ago Closed 13 years ago

Resizing tab groups does no longer "snap size" to other groups

Categories

(Firefox Graveyard :: Panorama, defect)

5 Branch
x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 659476

People

(Reporter: dasschwarzeloch, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 In FF4 during both moving and resizing tab groups the position / size "snapped in" when reaching the borders of another tab group. In FF5 this behaviour only applies to moving the group, not to resizing. Reproducible: Always Steps to Reproduce: 1. Have at leaste two tab groups 2a. Move one group - it snaps when coming across the borders of group two 2b. Resize it - no snapping here
Version: unspecified → 5 Branch
Mozilla/5.0 (Windows NT 5.1; rv:7.0a1) Gecko/20110622 Firefox/7.0a1 Works for me, the groups in Panorama are "snapping in" when changing/resizing their position in Firefox 4, Firefox 5 or the latest Firefox nighly. Reporter, please can you confirm whether this issue still occurs using Firefox in safe mode and/or with a clean profile? http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile
Confirming the bug with both a new profile and in safe mode. Observed on two machines: 1. Windows 7 64 Bit 2. Windows XP 32 Bit To be precise on the version - it is the version of the latest auto-update, namely 5.0 as written in "About firefox".
I can confirm this also on Ubuntu 11.04 (x86). Note that this only occurs when using the corner resizer. It’s not an issue when the group is created initially by dragging in an empty space. Also, for some reason, this is not an issue in the latest nightly.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.