Closed Bug 253495 Opened 22 years ago Closed 22 years ago

Location bar and Tabbed Browser have different favicons

Categories

(Firefox :: Address Bar, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: rvecchiolli, Assigned: bugs)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 The site listed above and many of the other user sites display different favicons in the location bar and in the tabbed browser. The favicon that shows up in the tabbed browser is the correct favicon for the site. The favicon that shows up in the location bar is the favicon located in the server root. See the following two examples: http://nunyas.dyndns.org/~max http://nunyas.dyndns.org/~lvillegas Reproducible: Always Steps to Reproduce: 1. Go to http://nunyas.dyndns.org/~max or http://nunyas.dyndns.org/~lvillegas 2. Notice that the favicon that appears in the location bar is different from the favicon that appears in the tabbed-browser. 3. The correct user favicon is displaying in the tabbed-browser, while the location bar is displaying the server root favicon. Actual Results: The location bar displayed the server root favicon, and the tabbed browser displayed the "correct" user favicon Expected Results: The user favicon should have been displayed in both the location bar and the tabbed browser. This is the only website that I've seen exhibit this particular problem with Firefox. It does not seem to be theme dependant since friends that are also using Firefox (with different themes) are also reporting the issue to me.
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040727 Firefox/0.9.1+ Can be a dupe of a fixed bug. Maybe 174265?
please report bugs only if they can be reproduced using nightly builds.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.