Closed
Bug 284771
Opened 20 years ago
Closed 20 years ago
Intermittent rendering errors on www.ebuyer.com
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: shumatsu_samurai, Assigned: bugzilla)
References
()
Details
Attachments
(1 file)
|
84.23 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050226 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050226 Firefox/1.0.1 If one browses ebuyer.com with Firefox (1.0 or 1.01), the page can appear incorrectly displayed. Internet Explorer consistently views ebuyer without any errors. It appears that CSS is not being applied to the page. Reproducible: Sometimes Steps to Reproduce: 1. View any page on www.ebuyer.com 2. Chances of errors appearing are random
| Reporter | ||
Comment 1•20 years ago
|
||
This is how ebuyer.com (or any of its sections) is displayed when the error affects browsing
| Reporter | ||
Updated•20 years ago
|
Summary: Intermitent rendering errors on www.ebuyer.com → Intermittent rendering errors on www.ebuyer.com
Comment 2•20 years ago
|
||
WFM, Firefox 1.0.1 and Mozilla 2005-03-04-05 trunk Linux.
I get the same bug, but instead of getting the message in the screenshot posted earlier, I get this message: "Please note: You are seeing this message because your browser does not appear to support CSS. To view the site as it is intended please feel free to upgrade your browser to the latest version of any of the following. Firefox, Mozilla, IE 6, Opera or Netscape" I also get this intermitently. Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Comment 4•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050330 Firefox/1.0+ WFM
| Reporter | ||
Updated•20 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 5•20 years ago
|
||
For some reason the error no longer occurs on ebuyer.com. It is possible that the company upgraded their servers, so the problem was fixed. Please try to find out what may have been causing it, lest it happen again. Cheers
You need to log in
before you can comment on or make changes to this bug.
Description
•