Bug 74185
| Summary: | Webkit reports incorrect height for tbody | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Robin Whittleton <robin> |
| Component: | Tables | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ahmad.saleem792, ap, bfulgham, rniwa, simon.fraser, zalan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw%2BDQo8aHRtbCBsYW5nPSJlbiI%2BDQo8aGVhZD4NCjxtZXRhIGNoYXJzZXQ9IlVURi04IiAvPg0KPHRpdGxlPnRib2R5IGNvbXB1dGVkIGhlaWdodCB0ZXN0Y2FzZTwvdGl0bGU%2BDQo8c3R5bGU%2BDQoJdGFibGUgeyBiYWNrZ3JvdW5kOiBibHVlOyBib3JkZXItY29sbGFwc2U6IGNvbGxhcHNlOyAgfQ0KCXRkIHsgYmFja2dyb3VuZDogZ3JlZW47IGhlaWdodDogMTAwcHg7IH0NCjwvc3R5bGU%2BDQo8L2hlYWQ%2BDQo8Ym9keT4NCjx0YWJsZT4NCgk8dGJvZHk%2BDQoJCTx0cj4NCgkJCTx0ZD5IZWlnaHQ6IDEwMHB4OzwvdGQ%2BDQoJCTwvdHI%2BDQoJPC90Ym9keT4NCjwvdGFibGU%2BDQo8YnV0dG9uIG9uY2xpY2s9ImFsZXJ0KGdldENvbXB1dGVkU3R5bGUoZG9jdW1lbnQuZ2V0RWxlbWVudHNCeVRhZ05hbWUoJ3Rib2R5JylbMF0pLmdldFByb3BlcnR5VmFsdWUoJ2hlaWdodCcpKSI%2BQWxlcnQgdGJvZHkgaGVpZ2h0PC9idXR0b24%2BDQo8L2JvZHk%2BDQo8L2h0bWw%2BDQo%3D | ||
Robin Whittleton
Querying the computed style on a tbody results in a size 2px bigger than visible. See attached testcase.
Expected:
---------
Clicking the button shows the tbody as being 100px tall.
Actual:
-------
Clicking the button shows the tbody as being 102px tall.
Browsers:
---------
Chrome 15 and Safari 5.1.2 alert 102px.
Firefox 9 and Opera 11.60 alert 100px.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Robin Whittleton
Just revisited this and today’s Firefox Nightly is reporting 102px as well. I guess this turned out to be a Firefox bug, although I’m not sure what the root problem is.
Ahmad Saleem
I am unable to reproduce this bug and all browsers show "102px":
> Safari Technology Preview 151 / Safari 15.6.1 - 102 px
> Firefox Nightly 105 - 102 px
> Chrome Canary 106 - 102 px
Further, Comment 01 confirms that it was Firefox bug and seems to be fixed and now all browsers are matching. Going to mark this as "RESOLVED INVALID". Thanks!