Closed
Bug 218301
Opened 22 years ago
Closed 21 years ago
{inc}After clearing cache or visiting site for first time, pages using simple three column table and CSS render incorrectly
Categories
(Core :: Layout: Tables, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ryan, Unassigned)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827
Pages at www.exegenix.com will occasionally throw the content of a three column
table to the far right of an absolutely-positioned image object. Reloading(and /
or SHIFT-Reload) the page usually rerenders properly.
Reproducible: Sometimes
Steps to Reproduce:
1. Shut down Mozilla
2. find your CACHE folder and delete all files (Note that using Mozilla's "clear
cache" doesn't actually delete ALL The files in the cache folder; do this manually)
3. Browse pages at www.exegenix.com; pages will occasionally, unpredictably,
render incorrectly, with the contents of a three column table that should be
layered on top of the background image object, thrown off to the far right, in a
table that is NOT just moved, but mashed to some kind of minimum width.
When the error is seen, it looks like the "background" image, for which the
markup falls outside (before) the TABLE, is being handled as though it was
inside the table.
Symptom: seems to occur when a page is not loading immediately... some kind of
delay is noticable, then the page doesn't render properly.
Comment 1•22 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827
Seeing the same behavior... Doesn't seem to occur when you enter the URL and hit
"GO" and reloading doesn't always fix it. It's random-seemingly.
Reporter | ||
Comment 2•22 years ago
|
||
I have made a screenshot of available at
http://www.exegenix.com/images/screenshots/exegenixdotcomscreenshot2.png
I was able to see the bug once, but couldn't reproduce it again after that.
Depends on: 217590
Comment 4•22 years ago
|
||
I had a quick look at this, and almost Confirmed it, until I had a look at the
page source. Now, I don't fully understand the <div> tag yet, but it looks to me
that the greyish background image has been coded as a non-background image.
Hence the problem.
This is definitely a bug. The reason it's not confirmed is that it lacks a
simple testcase.
Comment 6•22 years ago
|
||
Comment 7•22 years ago
|
||
What is supposed to lay on 85% of the page is compressed on a hundredth of
pixels on the right, after the left column using 100% of the table's width.
Comment 8•22 years ago
|
||
I experienced this problem this morning on a site with a classical 3-column
layout using the TABLE element.
I'm using Mozilla 1.4 from Debian Unstable, hence on Linux. It has been last
updated about a couple of weeks ago.
Silly I experienced it only this morning altough the general layout is quite
popular on the Web and we use it internally.
I cannot enclose a URL since it's an internal site but I enclosed two screen
shots. The first one is the expected rendered page, the second one is what I get
sometimes but not always.
My cache parameters are that the page is compared once per session.
Finally, the HTML and CSS have been proven to be syntaxically correct by the W3C
validators.
Reporter | ||
Comment 9•22 years ago
|
||
Connecting via dialup, more often than not the rendering behaviour is INCORRECT.
It may therefore be linked to some timeout condition.
Summary: After clearing cache or visiting site for first time, pages using simple three column table and CSS render incorrectly → {inc}After clearing cache or visiting site for first time, pages using simple three column table and CSS render incorrectly
Comment 10•21 years ago
|
||
WORKSFORME,
Mozilla nightly trunk build 2003-12-12-09 on Linux
Mozilla nightly trunk build 2003-12-12-09 on Windows 98 SE
(Most likely fixed by bug 215857)
(See also bug 217590 comment 25)
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•