(In reply to Mats Palmgren (:mats) from comment #4)
So, given our box tree, I think the current rendering is correct.
Normally, overflow != visible makes the scroll frame the abs.pos.
container and by default everything that is top/left of the scroll
origin is clipped.
I didn't think overflow:hidden could be the issue. Thanks for debugging this.
I guess we could make the (outer) nsFieldsetFrame the abs.pos.
container instead (for children of the "rendered legend" only),
but that might cause other issues...
Right. It's doable to reparent absolute frames, but it's a rare practice in our frame constructor.
We should probably wait for Chrome to fix this bug first:
I suspect that if they do, they might get the same rendering
for these testcases.
<fieldset> with overflow scrolling on Chrome looks so wrong to me ;)