Closed Bug 541557 Opened 16 years ago Closed 16 years ago

Tab Separation Feature Shows Apparent Debugging Message When Tab Is Dragged Into A Content Area [caused by Split Browser]

Categories

(Firefox :: Extension Compatibility, defect)

3.6 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: aroni125, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) The feature that allows tabs to separate from their original browser windows seems to have a debugging message enabled for when a tab is dropped onto the conent area. The message produced is 'TypeError: dt.getData("application/x-moz-tabbrowser-tab").linkedBrowser is undefined'. This is not reproducible when it is dropped outside the browser window. Reproducible: Always Steps to Reproduce: 1. Setup: Open a new tab. 2. Reproduce: Drag newly created tab into the content area. Actual Results: The message mentioned in "Details" appears. Expected Results: The message should have been suppressed, as the separation still occurred. I was running Tab Mix Plus at the time. I will post a message when I attempt to reproduce with it disabled.
Version: unspecified → 3.6 Branch
I have narrowed it down to the "Split Browser" addon, which I did not think was relevant. It is only reproducible with that addon. I will notify the developer.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Thanks Joshua for tracking down that problem and notifying the add-ons author!
Component: Tabbed Browser → Extension Compatibility
QA Contact: tabbed.browser → extension.compatibility
Summary: Tab Separation Feature Shows Apparent Debugging Message When Tab Is Dragged Into A Content Area → Tab Separation Feature Shows Apparent Debugging Message When Tab Is Dragged Into A Content Area [caused by Split Browser]
You need to log in before you can comment on or make changes to this bug.