Closed
Bug 306084
Opened 20 years ago
Closed 20 years ago
Move Tab to New Window crashes when only one tab is open [@ objc_msgSend]
Categories
(Camino Graveyard :: Tabbed Browsing, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino1.0
People
(Reporter: chiefaesthete, Assigned: sfraser_bugs)
Details
(Keywords: crash, fixed1.8)
Crash Data
Attachments
(1 file)
|
22.63 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050826 Camino/0.9a2+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050826 Camino/0.9a2+
When moving tabs to a new window using the relevant context menu option, and
only one tab is open, the browser crashes. (Using the feature with two or more
tabs open works as expected.)
Reproducible: Always
Steps to Reproduce:
1. Make sure that "Always show tab bar" is enabled in Preferences and that only
one tab is open.
2. Control- or right-click the tab.
3. Select "Move Tab to New Window" from the resulting context menu.
Actual Results:
Browser opens contents of tab in new window, but then immediately crashes.
Expected Results:
The browser should not have crashed, or the option to move tabs into new windows
should be disabled when only one tab is open. (Seems a little silly that it
would even be allowed in the first place.)
I see this too, recent trunk build.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Move Tab to New Window crashes when only one tab is open → Move Tab to New Window crashes when only one tab is open [@ objc_msgSend]
Keywords: crash
Comment 3•20 years ago
|
||
Shouldn't we just not allow this?
And does this only happen on the trunk or on the branch as well?
CCing Simon.
| Assignee | ||
Updated•20 years ago
|
Assignee: pinkerton → sfraser_bugs
| Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → Camino1.0
| Assignee | ||
Comment 4•20 years ago
|
||
Fixed on trunk and branch.
Updated•14 years ago
|
Crash Signature: [@ objc_msgSend]
You need to log in
before you can comment on or make changes to this bug.
Description
•