Closed Bug 144247 Opened 23 years ago Closed 22 years ago

Ctrl+W closes browser instead of just that tab when cursor in input field

Categories

(SeaMonkey :: Tabbed Browser, defect)

Product:
SeaMonkey
Component:
Tabbed Browser
Platform:
x86
FreeBSD
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: clay, Assigned: jag+mozilla)

References

(
URL
)

Details

If, with multiple tabs open, you place the cursor in an input field (which I believe it defaults to) and then hit ctrl-w, the whole browser closes instead of just that tab. This happens with certain input fields (such as the above page and http://www.wordsmith.org/anagram/ for example) but not others (such as Google). This is in v1.0rc1 on FreeBSD 4.5, I have not had opportunity to test other versions/platforms.
This is probably a duplicate of bug 108973.
Sounds more like something's crashing for ctrl+w in textfields on freebsd.
QA Contact: sairuh → pmac
Just to do some followup.. I played with this on: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021026 Phoenix/0.3 and I get no response at all from ctrl-w within an input box.
Phoenix might be the wrong product to test. On Linux, ctrl+w in any textfield means move back a word, which overrides the global ctrl+w for "close a tab/window".
WFM Mozilla 1.2 beta Windows 98. Are you sure you didn't just hit Ctrl+Q? Are you sure that Mozilla is closing? Or did the browser crash? Reporter, can you please try this on a new, trunk build of Mozilla?
Summary: Ctrl-W closes browser instead of just that tab when cursor in input field → Ctrl+W closes browser instead of just that tab when cursor in input field
I'm using build ID 20030315 on linux. Hitting Ctrl-W inside an input field causes the word preceeding the cursor to be erased. This matches the keyplan (see <http://www.mozilla.org/projects/ui/accessibility/mozkeyplan.html>). Clayton, can you reproduce this with a current copy of mozilla? Could you try to determine whether mozilla is crashing or just exiting? Please try running mozilla from the command line and see if it produces any error messages. Or if you know how to run gdb, run "/path/to/mozilla -g" from the command line; this starts gdb and lets you run mozilla from there.
I am no longer able to reproduce this issue. It is certainly gone in 1.2.1, and possibly was gone in 1.1 as well.
Resolving per comment 7. Thanks for the update, Clayton!
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.