225296 - links only type ahead find followed by find in page for same text tfinds only links

Status: RESOLVED WORKSFORME

(SeaMonkey :: Find In Page, defect)

Description

[Michael Meisel]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031110 Camino/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031110 Camino/0.7+

If accessibility.typeaheadfind.linksonly is enabled in user.js, once
type-ahead-find has been used on a page, searching with the find in page dialog
also only finds links.

Reproducible: Always

Steps to Reproduce:
1. Enable accessibility.typeaheadfind.linksonly in user.js
2. Open a page with a lot of text and links such as versiontracker.com
3. Use type-ahead-find to search for a string that appears both inside and
outside of link text on the page
4. Use the find in page dialog to search for the same string

Actual Results:  
Only matches within links are found. Also, wrap around seems to stop working.

Expected Results:  
The find in page dialog should always find all matches, independent of the
type-ahead-find setting and whether or not it has been used on the current page.

Comment 1

[Derek Schrock]

I think this is a Gekco problem. The same thing happens in Mozilla.
Product should be changed to Browser and Component should be Keyboard: Find as
you Type.
Also I would assume this is happens by design.

Comment 2

[Michael Meisel]

If this is in fact by design, I would like to voice my strong dissent. I use
type-ahead-find to avoid having to use the mouse to follow links as I have RSI
and find mouse usage painful. I have to type many more characters if
type-ahead-find searches the other text on the page as well, so I prefer to
limit it to links. But I don't want to lose the ability to search the other text
on the page! Perhaps there could be separate preferences for type-ahead-find
links only and find dialog links only?

Comment 3

[Derek Schrock]

Change of Product and Component

Comment 4

[Aaron Leventhal]

The problem is that you're using the same text. Find as you type doesn't know
that new text is being searched for. It's a legitimate bug -- I would welcome a
fix from the community.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[David Bolter [:davidb] (NeedInfo me for attention)]

Mass un-assigning bugs assigned to Aaron.

Comment 7

[Jens Hatlak (:InvisibleSmiley)]

This bug exists with SM 2.0, but will not be fixed there (branch receives only security fixes and simple/safe changes).

WFM with current SM 2.1 trunk nightly build:
1. Go to http://www.seamonkey-project.org/
2. Type "release". This find the "SeaMonkey 2.0.10 Release Notes" link using the "Quick Find (links only)" bar.
3. Press Ctrl+F. This opens the findbar with "release" prefilled. Pressing Enter cycles through three links and one text match on the page, and repeats at the top of the page when the bottom is reached.