Closed
Bug 265379
Opened 20 years ago
Closed 17 years ago
When using the fast find feature in 1.0, it doesn't scroll to the found item, however it will hilite in certain situations
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: admin, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 While editting the CSS file through the Admin Control Panel of my Invision Power Board (version 2.0.1) I attempted to use the fast find to locate some code. In version 0.9.3 the floating finder worked perfecly and caused the window within the ACP to scroll directly to the code. The static new fast find however will not do this. I attempted different cursor pacemnts to try and activate the frame but it made no difference. It will however hilite the code placed into the input box, but lacks the ability to cause the scroll in the frame to auto-scroll. Reproducible: Always Steps to Reproduce: 1.Ctrl+F in IPS ACP during editting of code which has a scrolling frame 2.Enter code, press submit 3. Actual Results: Returns value of code not found and no scrolling happens even though code gets hilighted. Expected Results: Frame should have scrolled to the code specified for.
Same with the latest firefox port to feebsd Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041030 Firefox/1.0RC1 also the '/' shortcut to do a search and the search for links do not work
Updated•19 years ago
|
Assignee: bugs → nobody
QA Contact: bugzilla → toolbars
Comment 2•18 years ago
|
||
Does this still occur using a recent release (2.0.0.3) or a nightly build (http://mozilla.org/developer)? If not, please close as WORKSFORME.
Comment 3•17 years ago
|
||
still no response, marking incomplete, feel free to reopen if you can reproduce with the current version
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•