Closed Bug 30308 Opened 25 years ago Closed 25 years ago

CSS Style is lost upon a reload of this page

Categories

(Core :: CSS Parsing and Computation, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED DUPLICATE of bug 29370

People

(Reporter: jrgmorrison, Assigned: pierre)

References

()

Details

http://www.zdnet.com/pcweek/stories/jumps/0,4270,2411217,00.html Overview Description: CSS Style is lost upon a reload of this page. This is a follow-on from bug #22185. That bug is fixed (I believe) and it dealt with a different problem. However, while looking at this bug again I noticed that the CSS for some of the text is not reapplied to the page when the page is reloaded. Steps to Reproduce: 1) Start the browser. 2) Load the URL http://www.zdnet.com/pcweek/stories/jumps/0,4270,2411217,00.html 3) Notice that (among other examples on the page) the text "ZDNet > Business & Tech > PC Week > Reviews" is in a sans-serif font. 4) hit the reload button (or View -> Reload, or set focus in URL bar and hit Enter). 5) Notice that the text "ZDNet > Business ..." is now in a serif font. Actual Results: CSS font-family not re-applied when the page is reloaded. Expected Results: CSS style should be the same in either initial load, or a reload. Reproducibility: Always. Build Date & Platform Bug Found: opt comm win32 bits for 03/03 (but the build ID claims 2000022708 which is wrong (known problem)). P500, 128MB RAM, HP Kayak. Additional Builds and Platforms Tested On: Also occurs on (stole elig's machines): Linux (2000030308 AM optimized build) Vectra VL (266 MHz P2), 96 MB RAM. Red Hat Linux 6.0 (GNOME). Doesn't Occur On Mac OS (2000030308 AM optimized build) [Power Mac G3 (266 MHz PowerPC 750), 96 MB RAM (VM on; 1 MB of VM used), 1024x768 (Thousands of Colors), Mac OS 8.6 [This was surprising to me -- before I tested, I'd assumed this would be XP).
*** This bug has been marked as a duplicate of 29370 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
VERIFIED DUP
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.