Closed Bug 285282 Opened 20 years ago Closed 19 years ago

Browser functions (find, address bar) work, but not functioning on current tab

Categories

(Firefox :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED EXPIRED

People

(Reporter: kasey.krehbiel, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

I've seen these separated but not together, and being a computer programmer
myself, I believe they are one and the same problem. When I open Firefox 1.0.1,
(website doesn't matter) with one tab I can use the find commands and the
address bar shows the website correctly. If I open another website in another
tab, the new tab displays and the address bar reflects the URL of the new tab.
The find command  looks for text in the previous window!!! If I click back to
the first tab, I find that whatever I typed in the find field is in focus, and
the URL of the second site remains in the address bar. I believe this is a
problem with the browser functions not updating according to the
currently-clicked tab.

Reproducible: Always

Steps to Reproduce:
1. Open a website with Mozilla Firefox 1.0.1. (Website #1)
2. Open another website in a new tab. (Website #2)
3. Try to find something on Website #2. Search for a word that's on website #2,
but not on website #1.
4. Now search for a word that's on the Website #1, but not on Website #2.
5. Click back to Website #1.

Actual Results:  
1. Firefox opens (wow) with Website #1.
2. Website #2 opens in a new tab.
3. The search term is NOT FOUND, even if the word is right there in front of my
face on the current site.
4. The search term IS FOUND... hmm
5. The address of Website #2 remains in the address bar (even though Website #1
has focus) and the search term I typed in earlier that was found from the other
tab is focused (it's ALWAYS on the screen but not always highlighted)

Expected Results:  
1. Did what it should have done.
2. Same.
3. It should have found the search term for the current page.
4. It should NOT have found the search term (because it's not on the current page!)
5. The address bar should have updated to reflect the page I'm really on.

This bug happens with a standard outta-the-box Mozilla Firefox 1.0.1 install. It
happens on 3 different computers with different configurations. Two computers
use Windows XP Pro Service Pack 2, and the other uses Windows XP Pro Service Pack 1.

I do a lot of web developing using Firefox (html, css, javascript) [because IE
bites] and it's annoying not to be able to use tabs (I can't use them because
the find function is broken if I use more than one tab!) I also kind of need to
be able to see exactly which address I'm on, because many of the sites I have
are quite similar.
WFM using Mozilla/5.0 (X11; U; Linux i686; sv-SE; rv:1.7.5) Gecko/20050221
Firefox/1.0 (Ubuntu) (Ubuntu package 1.0+dfsg.1-6ubuntu1).
I can confirm this is happening to me too. (at least under Windows. I'll try
under Gentoo Linux later on.)

I think the "Page search" functionnality is bound to the tab that was active
when the search begun. In my case (right now) I opened two tabs and begun
searching with the second one. I then switched to the first tab and wanted to
search again in that tab. It was actually searching on the second tab, which I
begun searching in.

This is happening with Firefox 1.0.2 as I'm reluctant to upgrade. (I've already
got my profile corrupted right after an upgrade to 1.0.3.) So I don't know if
this bug has been solved in version 1.0.4, which is available today.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.