Closed
Bug 606429
Opened 14 years ago
Closed 14 years ago
After drag & drop tab in tabstrip, Panorama group become collapsed and tab is grouped wrongly
Categories
(Firefox Graveyard :: Panorama, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Firefox 4.0
People
(Reporter: alice0775, Unassigned)
References
Details
Attachments
(1 file)
65.37 KB,
image/png
|
Details |
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101020 Firefox/4.0b8pre ID:20101020120347 After drag & drop tab in the tabstrip, Panorama group become collapsed and tab is grouped wrongly(unintentionally). Reproducible: Always 1. Start Minefield with new pofile 2. Open 3 tabs (now [ A ][ B ][ C ][+]) 3. Pinned 1st and 2nd tab (now [A][B][ C ][+]) 4. Enter Panorama, and exit Panorama 5. Drag & drop 1st pinned tab to left sideof [+] (now [B][ C ][ A ][+]) 6. Enter Panorama Actual Results after step6: Panorama group become collapsed. (See Attached screen shot) 7. exit Panorama Actual Results after step7: missing tab[ A ] Expected Results: Panorama makes tab groups unintentionally Panonara group shoul be display correctly
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 1•14 years ago
|
||
I suspect this will be fixed when bug 598600 lands, though it doesn't appear to be a duplicate.
Depends on: 598600
OS: Windows 7 → Windows XP
Updated•14 years ago
|
Flags: in-litmus?(twalker)
Comment 2•14 years ago
|
||
Alice, now that bug 598600 has landed on mozilla-central, can you still repro this?
Reporter | ||
Comment 3•14 years ago
|
||
Works on http://hg.mozilla.org/mozilla-central/rev/d253c44465ae Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101026 Firefox/4.0b8pre ID:20101026042359
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Comment 5•13 years ago
|
||
Added testcase in Litmus - https://litmus.mozilla.org/show_test.cgi?id=15308 as per flag in litmus was set.
Flags: in-litmus?(twalker) → in-litmus+
Assignee | ||
Updated•8 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•