Closed Bug 227519 Opened 21 years ago Closed 21 years ago

SearchToolbar forgets the last settings

Categories

(Firefox :: Toolbars and Customization, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 205708

People

(Reporter: nahor.j+bugmoz, Assigned: hyatt)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031202 Firebird/0.7+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031202 Firebird/0.7+ I usually set the search toolbar to use Google instead of "Find in this page". It used to work fine but now, it sometimes forgets my setting and revert back to the default ("Find in this page") Reproducible: Always Steps to Reproduce: 1. Make Firebird your default browser. 2. Set the toolbar to search Google. 3. Exit Firebird 4. Restart Firebird by double cliking on the executable (or the shortcut but NOT on an HTML document). Google should still be selected (sometimes it doesn't), if not, go back to step 2. 5. Exit Firebird. 6. Double click on an HTML document. Actual Results: Firbird opens and reset the search toolbar to the default "Find in this page". Expected Results: The search toolbar should still be Google. Sometimes, I can see Firebird displayign the Google icon for a short time before displaying the magnifier glass. Also, as I said in step 4, sometimes just restarting Firebird by double cliking on the executable resets the setting. But opening Firebird with a document always resets it.
Works for me, Google was still there both after normal restart and opening HTML document. Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.6b) Gecko/20031203 Firebird/0.7+
Still broken for me (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031203 Firebird/0.7+)
I got it to work a few times with an HTML document too. But it was a very simple one. I think the problem is a timing issue that's why it fails sometimes with a normal restart. Blair, try with a more complex document. My system is a bi-Athlon MP 1900+.
OK, I saved a complex page (67kb page + 574kb images) and tried it. It worked without a problem. If you want to upload as an attachment a file that it won't work for you with (put it along with images etc in a zip file), then I will give it a go with that document. My system is a helluva lot worse than yours.
I have to retract what I said about timing. Here is what I dicovered. If I start Firebird with a quicklaunch icon (no parameters) or if I load Firebird using the "Run..." from the Start menu, Firebird loads in state, say, A. If I start Firebird by double-cliking on an html document, Firebird loads in state B. Now, if I set the setting for the search bar in one state, and if the following time I restart Firebird in the same state, the setting is remembered. However, if I set the setting in one set, then load Firebird in the other state, then the setting is reset. That explains why "sometimes" I got the setting reset even when starting Firebird without document. As for what kind of HTML document, any will do. Even small ones. Even an empty document (without any tag what so ever). If I couldn't reproduce it with a very simple document before was because I always loaded and set the setting when in "state B". I tried on another WinXP Pro machine and it didn't work either. I tried on a Japanese Win2K Server and on a WinXP Media Center but there it worked. For WinXP Pro and the Win2K Server machines, it was completly fresh installs (no profile or previous version of Firebird on them) (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031207 Firebird/0.7+)
*** Bug 227814 has been marked as a duplicate of this bug. ***
Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Nominating for 0.8 blocker. Real annoying, happens often.
Flags: blocking0.8?
*** This bug has been marked as a duplicate of 205708 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Flags: blocking0.8?
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → toolbars
You need to log in before you can comment on or make changes to this bug.