a lot of display errors when opening apple.com

RESOLVED INVALID

Status

()

RESOLVED INVALID
14 years ago
13 years ago

People

(Reporter: s5490569, Assigned: bugs)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.5 (KHTML, like Gecko) Safari/125.11
Build Identifier: 

In the page at http://www.apple.com everything looks wrong. No specific things, but everything is 
wrong.

Reproducible: Always
Steps to Reproduce:
1. try to open http://www.apple.com
2.
3.
Actual Results:  
false rendering of the page

Expected Results:  
correct rendering of the page

Comment 1

14 years ago
And what's your base for comparison?
(Reporter)

Comment 2

14 years ago
(In reply to comment #1)
> And what's your base for comparison?

For example Internet Explorer. On Mac OS X Firefox is displaying the site right. If you want I can sent 
you a screenshot of the page.

Comment 3

14 years ago
I dont see any difference, can you please attach a screenshot to the bug?
https://bugzilla.mozilla.org/attachment.cgi?bugid=268238&action=enter
(Reporter)

Comment 4

14 years ago
Created attachment 165040 [details]
screenshot of display bug of apple.com

sending screenshot as required

Comment 5

14 years ago
Are you blocking the images? Can you retry in safe mode? Or a fresh profile?
(Reporter)

Comment 6

14 years ago
(In reply to comment #5)
> Are you blocking the images? Can you retry in safe mode? Or a fresh profile?

Sorry, I've checked my firewall (AtGuard) and it was causing the error with the page.

Comment 7

14 years ago
Based on reporters comment
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
--> Websites :: www.mozilla.com so timeless can close out Firefox :: Product Site.
Component: Product Site → www.mozilla.com
Product: Firefox → Websites
-> Firefox::General (939393)
Component: www.mozilla.com → General
Product: Websites → Firefox
You need to log in before you can comment on or make changes to this bug.