Martijn Wargers (dead) Reporter
	Description • 17 years ago

See url, I get a scrollbar in current trunk build, while I didn't get one in branch builds. It's happening because of the ads on the right.
This regressed with the landing of the reflow branch.

	Martijn Wargers (dead) Reporter
	Comment 1 • 17 years ago

Testcase that uses display: inline-block; instead of overflow: hidden;.
Notice the difference.

	Hallvord R. M. Steen [:hallvors]
	Comment 2 • 9 years ago

Hi Martijn, I don't see scrollbars but I note that Chrome and Opera (presto) render those TCs differently - the boxes are laid out horizontally instead of vertically. Is the issue this was reported for fixed but the test cases happen to show a different issue?

	Martijn Wargers (dead) Reporter
	Comment 3 • 9 years ago

Hallvord, I don't really know if this is considered an issue or not. I guess this is where it is defined in CSS: http://www.w3.org/TR/CSS21/visudet.html#the-width-property
David or Mats would know.

	David Baron :dbaron:
	Comment 4 • 9 years ago

Probably the closest thing to a spec is:
https://lists.w3.org/Archives/Public/www-style/2014Nov/0085.html

I'd be interested to know what WebKit/Chromium do differently.

	Mats Palmgren (inactive)
	Comment 5 • 9 years ago

I guess this depends on how "ISSUE 6" is resolved here:
https://drafts.csswg.org/css-sizing/#block-intrinsic

	Justin [:JW_SoftvisionQA]
	Comment 6 • 8 years ago

(In reply to Hallvord R. M. Steen [:hallvors] from comment #2)
> I don't see scrollbars but I note that Chrome and Opera (presto)
> render those TCs differently - the boxes are laid out horizontally instead
> of vertically.

I see the same when testing on Chrome and ie.

	Justin [:JW_SoftvisionQA]
	Comment 7 • 8 years ago

Are you still seeing a scrollbar?

	Mats Palmgren (inactive)
	Comment 8 • 8 years ago

I think this bug is more about whether the boxes are stacked vertically (Firefox)
or horizontally (Chrome).  Scrollbar or no scrollbar is a secondary concern.
There's still an issue noted in the spec about it, so this bug needs a decision
from the CSSWG before it can be resolved.

BTW, can someone test what Edge does?