Closed
Bug 302367
Opened 19 years ago
Closed 15 years ago
my.yahoo.com does not display correctly on second and subsequent viewing
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
INCOMPLETE
People
(Reporter: don, Unassigned)
References
()
Details
(Whiteboard: closeme 2009-08-01)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 When logging into my.yahoo.com it looks fine. After going to any other page or web site, then coming back to my.yahoo.com, the 'search bar' area at the top of the page displays incorrectly (square box, rather than long rectangle). I have to hit refresh one time to get it to display correctly. This happens each time I come back to the page from anywhere else. Reproducible: Always Steps to Reproduce: 1. (Must have a yahoo account) Log into my.yahoo.com using secure mode. 2. Go to any other page or web site. 3. Type in new URL my.yahoo.com (don't use back button) or if inside a yahoo page, click the 'My Yahoo' link. Actual Results: The Search Bar at the top of the page display incorrectly. Expected Results: Displayed the Search Bar correctly. When using Internet Explorer, it works perfectly fine. This has happened starting with version 1.0.5. When I removed and reinstalled 1.0.4 the problem did not go away. Screen shots of the problem can be provided upon request.
Comment 2•15 years ago
|
||
do you still see this problem? please update the bug with comment and/or close as appropriate. (bug has no comment since 2007-01-01)
Whiteboard: closeme 2009-08-01
Comment 3•15 years ago
|
||
No reply, INCO. Please reopen if you are seeing this in Firefox 3.5.2 or later in Firefox safe mode and a new profile with the latest plugins. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Profiles
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•