Closed Bug 246410 Opened 20 years ago Closed 20 years ago

No notification if find in page fails (Toolbar Search field)

Categories

(Firefox :: Search, defect)

x86
Windows 98
defect
Not set
minor

Tracking

()

RESOLVED FIXED

People

(Reporter: skydaemon80, Assigned: p_ch)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040608 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040608 Firefox/0.8.0+

Firefox does not display any sort of notification (message box or status bar
message) if a search for text in the current Web page from the Toolbar Search
field is unsuccessful.

Reproducible: Always
Steps to Reproduce:
1. Ensure that the Toolbar Search field is in "Find in this page" mode.
2. Enter some text that does not exist in the currently-displayed Web page, and
press ENTER.

Actual Results:  
Nothing happens.

Expected Results:  
Firefox should inform the user that the entered search term(s) was not found. 
This could be accomplished by using the same message box that displays when a
search fails when using Edit > Find in this Page, or a message should display in
the status bar (the latter option having the advantage of being less intrusive).
Still in 0.9 but it only appears when searching from the toolbar field (ctl+f
dialog is ok). Modifying summary.
Summary: No notification if find in page fails → No notification if find in page fails (Toolbar Search field)
With the introduction of the new Find Toolbar as of the 2004-07-07 nightly
build, this bug is no longer applicable.  The "Find in this page" capability in
the Web Search field is gone; it now searches the Web only.

However, the same problem seems to occur with the new Find Toolbar.  The old
status bar message,

   Text Not Found: "foo bar"

doesn't appear when a search is unsuccessful, unlike before with the original
Find As You Type feature.  I will file a new bug for that, if it has not already
been reported.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.