Closed Bug 131494 Opened 24 years ago Closed 24 years ago

Control+Enter in the URL bar does not open a tabbed window

Categories

(SeaMonkey :: Tabbed Browser, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 122035

People

(Reporter: moz-bugzilla, Assigned: jag+mozilla)

Details

(Whiteboard: DUPEME)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.9) Gecko/20020310 BuildID: 2002031005 Even if Preferences > Tabbed Browsing > Control+Enter in the URL bar is checked, using that key combination in the URL bar to open a web page in a tabbed window does not work. Reproducible: Always Steps to Reproduce: 1. Activate the preference item as indicated 2. Type a URL into the URL bar and press Control+Enter Actual Results: Nothing happens after I type the URL and hit the Control+Enter combination. This is occurring on an iBook Dual USB which has both the "standard" Return key and a smaller "Enter" key located to the right of the second Command key. Expected Results: Unless the purpose of the preference is unclear, the Control+Enter (i.e., the smaller Enter key next to the Command key) key combination should open a URL in a tabbed window as implied. Considering Mac users are not used to using the Control key, I would suggest making the Mac key combo into Command+Enter instead. In fact, I would also suggest treating Enter and Return as one and the same if they aren't already.
the control-enter key sequence is improperly processed on OSX. This is a problem throughout the browser (and there is a bug on it already, iirc).
Whiteboard: DUPEME
This is a duplicate of (at least) 122035. Marking as such. *** This bug has been marked as a duplicate of 122035 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
marking verified as a duplicate. if you decide to reopen this bug, please clarify why. search string for bugspam removal: SalviaGuaranitica
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.