Closed Bug 107845 Opened 23 years ago Closed 23 years ago

ctrl-t stops working when closing last but one tab

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME
mozilla1.1alpha

People

(Reporter: aleksander.adamowski, Assigned: jag+mozilla)

Details

(Keywords: crash)

Build ID: 2001103108 To reproduce: 1. Start Mozilla 2. Open a new tab (ctrl-t) 3. Close the second tab (Mozilla window gets back to no tabs mode) 4. Press ctrl-t again Result: no new tab is created Expected: new tab is created in the current window Additional info: After ctrl-t gets disabled, ctrl-n starts working like ctrl-t, that is ctrl-n opens a new tab instead a new window! I also observed crashes most probably related to this. I have talkback reports, but I can't send them ("unknown network error"). To reproduce crashes: Continuing from previous reproduction 5. Press ctrl-n several times to create alots of new tabs (seems that this step is required) 6. In any of these empty tabs open any web page 7. Try to switch to another tab with ctrl-pgup or ctrl-pgdn Mozilla should crash, but you may need to do some more messing with tabs and switching with ctrl-pgup, ctrl-pgdn
I've come up with a 100% reliable method of reproducing those crashes I mentioned. 1. Start Mozilla 2. press ctrl-t 3. close the tab 4. press ctrl-n 5. press ctrl-n (we now have 3 tabs) 6. close any tab 7. press ctrl-pgn or ctrl-pgup
Keywords: crash
One more thing worth noticing: After step 3, when you load a page with forms and You can't type anything into a text field or textarea.
Moreover, you can't type anything in URL bar. But when you press certain keys while inside a text field, they act as if they were pressed in conjunction with other keys or maybe as if their bindings have changed. Try for example pressing 'n' in a textfield (it will open a new tab just as ctrl-n would), or 'a'.
Reporter, try deleting your XUL.mfl file in your profile directory, and let me know if these problems persist.
That would be 'XUL.mfasl' on Linux, for the name of the fastload file. But, as of today's builds, that shouldn't be necessary, since if the mtime of the jar file from which some JS was serialized has changed, then the fastload file will be invalidated (deleted) and restarted.
Deleting XUL.mfasl doesn't help at all.
> Try for example pressing 'n' in a textfield (it will open a new tab > just as ctrl-n would), or 'a'. Actually, typing 'a' in a textfield seems to reconnect to the server. Try it and watch Throbber! Key combos (such as Ctrl+f) don't work either. (Oddly, Ctrl+n opens a new tab.)
I'm using Linux build 2001110821 and this seems to be fixed. Do you agree?
Looks like it's fixed in 2001-11-11-09, too.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Reassigning to new component owner.
Assignee: hyatt → jaggernaut
Status: ASSIGNED → NEW
Marking WFM per last few comments. Please reopen if the bug still exists.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.