Closed
Bug 181112
Opened 22 years ago
Closed 22 years ago
Keyboard focus does not work as expected after a failed DNS search
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Core
DOM: UI Events & Focus Handling
Tracking
()
VERIFIED
DUPLICATE
of bug 135363
People
(Reporter: nbobic, Assigned: aaronlev)
References
(Blocks 1 open bug)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021110
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021110
After typing a search string in an address bar and after pressing the Enter key
by a mistake (instead of down-arrow followed by an Enter) and after going back,
focus does not work as expected.
Reproducible: Always
Steps to Reproduce:
1. Type something in an address bar: "Dan Gillmor blog". This is the search
string we're trying to pass on to a search engine we've selected in Prefs.
2. Press Enter
3. We've made a mistake. Mozilla comes back and tells us that DNS failed for
that URL. Of course... we should have pressed down arrow followed by enter!
4. Click OK, move focus back to address filed using a mouse.
5. Press down arrow twice to select "Search Google for "Dan Gillmor blog""
6. Press Enter.
Actual Results:
Mozilla responds that it cannot load the URL because it is still trying to use
DNS to find "Dan Gillmor blog" website.
Expected Results:
Use Google.com and pass the string to it.
I use Pinstripe as my standard theme but this bug is reproducible with all other
themes that I've tried.
Confirmed using FizzillaCFM/2002110808.
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Comment 3•22 years ago
|
||
> Is this a Mac only bug?
No. It is reproducible under WinXP and Linux as well.
| Assignee | ||
Updated•22 years ago
|
OS: MacOS X → All
Hardware: Macintosh → All
*** This bug has been marked as a duplicate of 135363 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Component: Keyboard: Navigation → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•