The default bug view has changed. See this FAQ.

"Find Next" button doesn't always respond to Enter

VERIFIED FIXED in Phoenix0.2

Status

()

Firefox
General
VERIFIED FIXED
15 years ago
15 years ago

People

(Reporter: Nathan Silva, Assigned: Blake Ross)

Tracking

unspecified
Phoenix0.2
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20020924 Phoenix/0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20020924 Phoenix/0.1

In the "Find in this Page" dialog the "Find Next" button is the default button,
but it doesn't respond to the Enter key if you tab to one of the check boxes.

Reproducible: Always

Steps to Reproduce:
1. Choose Edit ยป Find in This Page...
2. Type something in the "Find what:" box.
3. Tab to the "Wrap" checkbox.
4. Press Enter.

Actual Results:  
Nothing

Expected Results:  
Enter should have activated the "Find Next" button.

Comment 1

15 years ago
unable to reproduce this. can you give me a page and a term to find where this
can be reliably reproduced. 
(Reporter)

Comment 2

15 years ago
Created attachment 100649 [details]
Hitting Enter should activate the "Find Next" button

This bug isn't specific to a particular web page. It has to do with the button
focus in the Find dialog. In this image, notice that the Wrap checkbox is the
active control, and that the "default" highlight is on the Find Next button.

If you hit Enter, it should behave as though you clicked Find Next. Instead,
hitting Enter does nothing.

Comment 3

15 years ago
You are correct. Sorry for misunderstanding. Confirmed with today's Phoenix
build on RH null.  
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
(Assignee)

Comment 4

15 years ago
Fixed.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Phoenix0.2

Comment 5

15 years ago
verified fixed. 
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.