Bug 146844 – Extra border space in table after a row has position: absolute

• Component: Tables
• Status: RESOLVED CONFIGURATION CHANGED

Created attachment 256596 [details]
Example of the table before hand.

In a table with 'border-collapse: separate', if a row has its style changed to include 'position: absolute', then extra border space is added to the table. This extra space then remains even if the row is switched back to the default 'position: static' or is removed from the table.

In this fiddle (which uses pure JavaScript, no jQuery or jQuery UI), you can add and remove rows and toggle a row between it's default of 'position: static' and an applied 'position: absolute'. When you toggle the position, I also change the color to a transparent red, so you can see what is going on a bit better. Once a row has been toggled to 'position: absolute', extra border space appears in the table. The extra space sticks around, even if you then toggle the row back to 'position: static' or remove it:  http://jsfiddle.net/3hffrur9/2/

This problem is occuring in Safari 7.1.7. It has been reported to me that it is also occurring in Safari 8.0.7 and Safari 9.0. And I have also now observed it in the current nightly build of WebKit (601.1.39).

Created attachment 256597 [details]
Table after toggling the second row to "position: absolute" and then back to the default "position: static"

[Ahmad Saleem]

I am not able to reproduce this bug in Safari Technology Preview 165, where clicking on 2nd row toggle and back does not lead to increase border width between first and second row and matches with the reference image of “Example of the table before hand”. Thanks!

This also does not reproduce in Safari 16.3, so it might be fixed long time back. Thanks!

As you might imagine, I had long ago forgotten about ever posting this bug.

In any case, I just tried this, and I agree that the problem no longer seems to exist.

Presumably, it has been fixed sometime in the last 8 years.

I've marked it RESOLVED FIXED - I'm not sure if WORKSFORME would be more appropriate, since I can't point to a specific fix - let me know.

Thanks,
Adam

[Alexey Proskuryakov]

We use Configuration Changed for issues that went away without a known fix. Thank you for confirming!