- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Mon, 14 Mar 2011 13:25:43 -0400
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: fantasai <fantasai.lists@inkedblade.net>, Peter Moulder <peter.moulder@monash.edu>, www-style@w3.org
On 3/14/11 1:02 PM, Tab Atkins Jr. wrote: > Firefox appears to simply always hide the marker when overflow is > non-visible, even though it positions outside markers according to the > list-item's first line, and thus the marker *should* be inside the > visible area and visible. It's not inside the visible area last I checked. See https://bugzilla.mozilla.org/show_bug.cgi?id=571564 which discusses what's going on in comment 0, but the short of it is that the visible area is the size of the list-item's content box or so, and the marker is outside that, so is clipped just like in IE or Webkit per your description. Note that I'm not sure what you mean by "positions outside markers according to the list-item's first line" here, but in Gecko the _vertical_ position is affected by the baseline of the first line while the _horizontal_ position is not affected by the first line at all. In particular, unlike Opera text-indent does not affect _outside_ markers in Gecko. Hope that makes it clear what the Gecko behavior is here and why. > So, all browsers appear to treat markers as always being children of > list-items. This part we agree on, I think. And I agree that this means that "scroll properly" is a huge PITA. See the bug referenced above. -Boris
Received on Monday, 14 March 2011 17:26:25 UTC