Closed
Bug 27323
Opened 25 years ago
Closed 25 years ago
indybox.com does not display well [4.xp]
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
CLOSED
WORKSFORME
People
(Reporter: sarnold, Assigned: leger)
References
()
Details
This page, has problems. The clear majority of images on the page load 'scrambled' -- (it even looked like some of the colors came from the little "mozilla button" -- where the old pulsating N used to be..) There are a multitude of colors, and very little gets positioned properly. Everything looks about what I imagine the designers intended under communicator 4.7 on the same platform. Will try for a screen shot. :)
Hmm, it appears that the attachment thingy is broken -- cannot attach files. So, I put the screenshot on my own webspace: http://www.willamette.edu/~sarnold/indybox.png
Comment 2•25 years ago
|
||
reporter - this is a worksforme and for other 2 linux users. I am marking this a worksforme. You are using a old build. Please get the newest one (m13 or a m14 nightly) and check the page again. If you still get this, please reopen.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Actually, the build-id given in the screenshot is invalid. I don't have a clue where that is set in the source, so I can't go about researching where it comes from. (Where *is* it set in the source? :) I made this screenshot with a build made with the CVS tree either on february 8th or 9th. I get very similar results with a build I made on the february 10th CVS as well. Who can I contact to ensure that my CVS scripts work properly? Who can I contact about that silly build-id problem? I would like to have faith that my bug reports aren't wasting any one's time. :)
Using the 02/15/00 CVS, this page no longer has wierd image corruption. (Tables still look a little goofy, but that deserves a seperate bug, depending on if it is a problem with their html or the table layouts.... :) Thanks :)
Status: RESOLVED → CLOSED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•