Closed Bug 648929 Opened 10 years ago Closed 10 years ago

frequently getting drag.info is null error in tabview.js

Categories

(Firefox Graveyard :: Panorama, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Firefox 6

People

(Reporter: fryn, Assigned: ttaubert)

Details

Attachments

(1 file, 1 obsolete file)

Upon selecting a group, I get the following error what seems to be every time:

Error: drag.info is null
Source File: chrome://browser/content/tabview.js
Line: 4118

at the line:
this.add(drag.info.$el, options);
in the method:
this.dropOptions.drop = function GroupItem_dropOptions_drop(event) { ... }
CC'ing mitcho, since he wrote the code.
Do you have an exact STR? I tried to reproduce but couldn't.
Can reproduce now. This happens every time you click on a tab to zoom into it.
Assignee: nobody → tim.taubert
Status: NEW → ASSIGNED
(In reply to comment #3)
> This happens every time you click on a tab to zoom into it.

That's actually what I meant. I must have been half-asleep when filing this.
Thanks for investigating and taking this bug. :)
Attached patch patch v1 (obsolete) — Splinter Review
Attachment #525541 - Flags: feedback?(raymond)
Attachment #525541 - Flags: feedback?(raymond) → feedback+
Attachment #525541 - Flags: review?(ian)
(In reply to comment #6)
> Passed try (kind of):
> 
> http://tbpl.mozilla.org/?tree=MozillaTry&pusher=tim.taubert@gmx.de&rev=a2426c7ed09f

Yeah, tryserver results are weird. I'd ignore the Android red though. :P
Comment on attachment 525541 [details] [diff] [review]
patch v1

Nice catch
Attachment #525541 - Flags: review?(ian) → review+
Attachment #525541 - Attachment is obsolete: true
Keywords: checkin-needed
http://hg.mozilla.org/mozilla-central/rev/84b1567baa32
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 6
Verified on Mozilla/5.0 (Windows NT 5.1; rv:6.0a1) Gecko/20110421 Firefox/6.0a1
Status: RESOLVED → VERIFIED
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.