Table rendered wrong (skips rendering some cells in some row)

RESOLVED INVALID

Status

()

Firefox
General
RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: Jose R. Cabanes, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b1pre) Gecko/20080926021032 Minefield/3.1b1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b1pre) Gecko/20080926021032 Minefield/3.1b1pre

Under some cases tables are rendered wrong. Tested on every Firefox 3 version, even nightly build. It worked nice on Firefox 2 and previous verions. 

Attached files show it. On a row in a table some cells in a row are not rendered, and the rest of cells in the same row are misplaced. Previous and later rows are rendered right. It happens on some rows but when it happens, it happens every time with that code.

Always I've observed this behaviour always when a CSS td:hover is present.

Reproducible: Always

Steps to Reproduce:
1. Browse attached HTML

Actual Results:  
Table is rendered wrong. Two cells on the seventh row (not counting header) are not rendered and the rest of cells on row are misplaced.

Expected Results:  
A table with all cells rendered.
(Reporter)

Comment 1

9 years ago
Created attachment 340599 [details]
Screenshot of the wrong behaviour
(Reporter)

Comment 2

9 years ago
Created attachment 340601 [details]
Code that reproduces the bug

Open file cby_orders.html in Firefox 3 (any version) and behaviour shown in image (see previos attachment) should be reproduced
(Reporter)

Updated

9 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
(Reporter)

Comment 3

9 years ago
Bug is not in rendering engine, but in AJAX. I've not been able to determine how to reproduce the bug and how to report in a useful way but seems that some bytes are not god from AJAX request. Sorry for the misunderstanding. I will try to do a more precisse report.
You need to log in before you can comment on or make changes to this bug.