See testcase, I would expect it to render the same as the reference rendering (which I'm going to attach). The only difference between the two is the addition of overflow: auto in the testcase.
So the issue is that moz-scrolled-content inherits the display... Should we instead be unconditionally setting it to display:block? That wouldn't affect scrolled blocks, would improve scrolled inline-blocks. The only question is what would happen with scrolled table-row-groups, but I think that should be ok.
Comment on attachment 341404 [details] [diff] [review] Like so You may wish to add a comment mentioning that this does not affect the type of frame created --- we always create the scrolled frame based on the real 'display' value of the element. So this is really just to satisfy code that checks whether the nsBlockFrame is inline-level.
Pushed changeset d28eb3aa049d with the comment change and the tests.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.