Closed Bug 321396 Opened 19 years ago Closed 17 years ago

JS error dragging tab to second window's tab/tab-strip

Categories

(SeaMonkey :: UI Design, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: stefanh, Unassigned)

References

Details

Mac OS 10.3.9 Seen on recent seamonkey trunk/branch. First appearance: 2005121412. 1. Open a browser window, load a few tabs. 2. Open a second browser window, load a few tabs. 3. Drag one tab from one window to the other window, drop the tab on either a tab or the tab-strip. Result: JS error in the console: "Error: aDragSession.sourceNode has no properties Source File: chrome://global/content/bindings/tabbrowser.xml Line: 1224" I have only confirmed this on mac, but I suspect it happens on all OS.
*** Bug 321394 has been marked as a duplicate of this bug. ***
I guess we need to (aDragSession.sourceNode && foo) in candrop, dragover, and dragexit (it seems drop is already protected).
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8) Gecko/20051219 SeaMonkey/1.0b] (release) (W98SE) SMv1.0b on Windows seems to work fine: URI are loading, with no JS.C output.
It probably depends on whether the widget code clears the source node for cross-window drags.
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20051223 SeaMonkey/1.5a] (nightly) (W98SE) SMv1.5a on Windows does not have this bug either. (Mac specific !?)
I can't repro this anymore (1.1.4 and trunk, 10.4.10).
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.