User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050804 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050804 Firefox/1.0+ In the testcase (http://swatinemz.sourceforge.net/testcase/) the rows 2 and 4 (which include images) are rendered as :last-child. Try toggling border-collapse and the bug is suddenly gone. The bug is not reproductible when the testcase is opened from a local drive. Reproducible: Always Steps to Reproduce: Actual Results: Wrong behavior: http://swatinemz.sourceforge.net/testcase/wrong.jpg Expected Results: Right behavior: http://swatinemz.sourceforge.net/testcase/right.jpg The testcase works fine in Firefox 1.0 (Gecko 1.7). Sorry for the rather complex testcase but i could not reproduce this bug with a simpler one.

This is a duplicate of or dependant on bug 73586.

I dont think this has something to do with #73586. First, it is not dynamic and secondly, it is a regression from gecko 1.7.

I don't see any good reason it should have worked in Firefox 1.0. Probably some other bug was covering it up.

WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050804 Firefox/1.0+ (exact same build as the reporter). Incremental layout issue? That would explain: "Try toggling border-collapse and the bug is suddenly gone.", "The bug is not reproductible when the testcase is opened from a local drive.", and "Sorry for the rather complex testcase but i could not reproduce this bug with a simpler one." Reporter (or anyone else who sees the bug), can you try changing the text size, then changing it back to default? (ctrl++, ctrl+-) and seeing if that fixes the problem? If it does, can you move it over to the layout component? (Also, make sure to "Reassign bug to owner and QA contact of selected component" and the dependency field will be wrong, so clear that too.)

I still notice this bug in the current nightly (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051014 Firefox/1.4.1) Changing the text size does not fix it for me.

It is dynamic since incremental loading of a page makes a series of changes to the page. *** This bug has been marked as a duplicate of 73586 ***