279285 - keyboard freeze opening invalid URL in new tab

Status: RESOLVED FIXED

(Firefox :: Keyboard Navigation, defect)

Description

[Ori Avtalion (salty-horse)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050120 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050120 Firefox/1.0+

When opening an invalid URL in a new tab (by middle-clicking, or right-clicking
and choosing the "open in new tab" option), focusing on the tab ignores any
keyboard input. The mouse still works.

Reproducible: Always

Steps to Reproduce:
1. Open the URL in a new tab by middle-clicking on it: http://dslkfjweiurei.abc
2. The "URL could not be found" message pops up.
3. Press the newly-opened tab.
Actual Results:  
Try to use the keyboard: CTRL+TAB, ALT+D, F6, CTRL+W .. no response.

Expected Results:  
The browser should respond to keyboard shortcuts.

Comment 1

[Ori Avtalion (salty-horse)]

This is a regression. The bug does not appear in Firefox 1.0

Comment 2

[Aaron Leventhal]

Did it regress from the checkin of bug 249136?
Does it make a difference if you open new tabs in the background or foreground?

Comment 3

[Ori Avtalion (salty-horse)]

(In reply to comment #2)
I just noticed that when opening tabs in the foreground, even valid ones, until
they ARE validated, the keyboard freezes.

Comment 4

[Frank Wein [:mcsmurf]]

This regressed between 2004-01-16-05 and 2004-01-17-07 so the checkin from Bug
249136 might have hit that build. Bonsai link:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-01-16+04%3A00%3A00&maxdate=2005-01-17+08%3A00%3A00&cvsroot=%2Fcvsroot

Comment 5

[Jesse Ruderman]

Confirmed in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b)
Gecko/20050121 Firefox/1.0+

Partial workaround: Use browser.xul.error_pages.enabled.  This workaround is
partial because it only helps once Firefox realizes the page won't load.

Comment 6

[Aaron Leventhal]

I'm sure this is from bug 249136. Shall I back that out?

Comment 7

[Frank Wein [:mcsmurf]]

(In reply to comment #6)
> I'm sure this is from bug 249136. Shall I back that out?

Would be nice if there isn't a fix in sight for this bug here.

Comment 8

[Frank Wein [:mcsmurf]]

*** Bug 281159 has been marked as a duplicate of this bug. ***

Comment 9

[Ben Fowler]

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050205
Firefox/1.0+

I came here from Bug 281159 . The manifestation on the Mac is (at least usually)
that such 'empty' Tabs close on the second application of Cmd-W or using the Close
Tab menu item with the mouse. 

The latter is sufficient work around, so this is a low priority bug.

(I can't actually remember a time when this defect was not in).

Comment 10

[Frank Wein [:mcsmurf]]

(In reply to comment #9)
> (I can't actually remember a time when this defect was not in).

I guessed you suffered from this regression here, since with Mozilla 1.7.5 for
example closing tabs with ctrl+w worked (but this a current trunk build it doesn't).

Comment 11

[Aaron Leventhal]

I think focus is probably somehow going to the DOM window itself.

Comment 12

[Aaron Leventhal]

Strike that, I forgot it's bug 249136. I'll back that out today and we'll look
for a new fix to bug 249136.

Comment 13

[Aaron Leventhal]

Fix for bug 249136 backed out.
Reopen if you still see a problem.