Open
Bug 560360
Opened 16 years ago
Updated 3 years ago
Table sizing is rendered incorrectly intermittently when css has comments.
Categories
(Core :: Layout: Tables, defect)
Core
Layout: Tables
Tracking
()
NEW
People
(Reporter: unimatrix.100, Unassigned)
Details
(Keywords: testcase, Whiteboard: qawanted)
Attachments
(3 files, 1 obsolete file)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Hi,
Please see the PHP source code file in the attachment. Once you've got it running, you'll have to force refresh the page a few times (for me it seems to always happen within 5 times), but you'll eventually see things like this (see attached image) - where there is a gap between two table rows. I can't quite put my finger on what is causing it, but it appears if the coments are removed from the css style, then this stops happening.
Reproducible: Sometimes
Steps to Reproduce:
1. Get the code in the above URL and run it from a php server.
2. Refresh until you see the above error.
| Reporter | ||
Comment 1•16 years ago
|
||
| Reporter | ||
Comment 2•16 years ago
|
||
| Reporter | ||
Comment 3•16 years ago
|
||
Attachment #440039 -
Attachment mime type: application/octet-stream → text/plain
Could be an incremental layout bug triggered by packet/buffer boundaries. If it is, it's probably possible to write a more reliable testcase using the offsetWidth hack.
Component: General → Layout: Tables
Product: Firefox → Core
QA Contact: general → layout.tables
Whiteboard: qawanted
(In reply to comment #4)
> Could be an incremental layout bug triggered by packet/buffer boundaries. If
> it is, it's probably possible to write a more reliable testcase using the
> offsetWidth hack.
Here we go.
Attachment #440039 -
Attachment is obsolete: true
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
OS: Windows XP → All
Hardware: x86 → All
Version: unspecified → Trunk
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•