Neil Skrypuch Reporter
	Description • 16 years ago

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.9 (like Gecko) (Gentoo)
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008122215 Gentoo Firefox/3.0.5

When you search for something in a page, the page will scroll down/up such that the search terms are in view, but only just barely. Normally, this isn't a problem, but http://wittyrpg.com uses (rather small) position: fixed; elements along the top (and bottom, after you're logged in) edges. Thus, if you search for something that isn't already visible, it still won't be visible after you "find" it, you'll need to scroll down/up after performing the find to see the search result.

Reproducible: Always

Steps to Reproduce:
1. Navigate to http://wittyrpg.com/faq.php
2. Scroll down a bit, enough that the first question in the index is outside the viewport.
3. Search for "What is this thing?"
Actual Results:  
"What is this thing?" is found, but not visible.

Expected Results:  
"What is this thing?" is found, and visible.

The FAQ page is only one example for this, you can find the same issue on most any page in Game!, especially the Inventory, as it pretty much always has scrolling and searching is frequently done.

The quick and easy fix for this would be to just put search results slightly closer to the center of the viewport (at least I assume it'd be (relatively) quick and easy), which is probably a good idea to start with. Konqueror for example puts search results a few ems down from the top of the viewport, and Opera centers them in the viewport.

There's a deeper issue here though, and that's the fact that position: fixed; elements can obscure search results (regardless of where the search results are put). A more elegant and complete solution would make sure that the search results are visible, wherever they're put, and if they wouldn't be visible in the normal spot, (if possible) scroll the page such that they are visible. I'm guessing this is a lot trickier, though.

	Tyler Downer [He/Him]
	Comment 1 • 14 years ago

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

	Neil Skrypuch Reporter
	Comment 2 • 14 years ago

Problem still exists in 3.6.10 exactly as originally described.