Closed Bug 1123185 Opened 11 years ago Closed 11 years ago

cannot drag tabs to reorder (caused by classic theme restorer add-on)

Categories

(Firefox :: Extension Compatibility, defect)

35 Branch
x86
macOS
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: mozilla, Unassigned)

References

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20150108202552 Steps to reproduce: Open two or more tabs. Click down on one tab and try to drag it to another location on the tab bar. Actual results: The entire Firefox window moves. Expected results: The tabs should be reordered.
Reinstalled Firefox 34 and it works as expected.
In 35, if you restart in safe mode (help > restart with add-ons disabled), does the same thing happen? Can you move the window on the screen in 35?
Severity: normal → major
Flags: needinfo?(mozilla)
Keywords: regression
Oh... are you using a custom Firefox theme? (see also: bug 1122942)
Thank you Gijs! I've localized it to Classic Theme Restorer 1.2.8.2 add-on. If I disable that, dragging works normally. BTW, yes, I could move the entire window on the screen by dragging the window frame. In fact, that's what it did when trying to drag a tab. - George
Flags: needinfo?(mozilla)
(Now, if only I could move the tab bar back down below the bookmarks toolbar.)
Thanks for getting back to us quickly! Sounds like something CTR needs to fix... :-(
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Component: Untriaged → Extension Compatibility
Resolution: --- → INVALID
Summary: cannot drag tabs to reorder → cannot drag tabs to reorder (caused by classic theme restorer add-on)
This is a CTR bug only occuring on MacOSX using "curved tabs (alt)" and "tabs not on top" options. However this is already fixed on beta builds and will be solved on release builds once CTR 1.2.9 is out. @George Dinwiddie No need to report CTR bugs on Bugzilla. CTR provides a support forum and you can contact me via email too.
You need to log in before you can comment on or make changes to this bug.