Closed
Bug 211112
Opened 21 years ago
Closed 21 years ago
Ctrl+click on a link that spawns a popup, kills the popup and displays a blank tabbed page
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 138198
People
(Reporter: shannont, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Steps to reproduce: 1. Hold Ctrl 2. Click on any link that spwans a pop-up Result: Pop-up is killed and a blank tabbed page is displayed. (NOTE: this occurs whether tabbed browsing is enabled or not) Expected: I'm not necessarily up on the correct behavior of tabbed browsing, but I would expect Ctrl+click should either display the pop-up correctly as a tabbed page or have no affect - unless there is an option in preferences to disable the Ctrl hotkey. Underlying Issue: Several pop-up killers allow the user to manually override the pop-up kill behavior w/ Ctrl+click. Reproducible: Always Steps to Reproduce: 1. Hold Ctrl 2. Click on any link that spwans a pop-up Actual Results: Pop-up is killed and a blank tabbed page is displayed. (NOTE: this occurs whether tabbed browsing is enabled or not) Expected Results: I'm not necessarily up on the correct behavior of tabbed browsing, but I would expect Ctrl+click should either display the pop-up correctly as a tabbed page or have no affect - unless there is an option in preferences to disable the Ctrl hotkey. Any easy place to reproduce this is cnn.com. Locate a QUICKVOTE box somewhere on the site, hold Ctrl and click VIEW RESULTS. If tabbed browsing is enabled, a blank, tabbed page called "Untitled" will display. If tabbed browsing is not enabled, a blank page is spawned on top of the main page.
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 138198 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•