- From: Bogdan Brinza <bbrinza@microsoft.com>
- Date: Tue, 17 Mar 2015 19:53:05 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: W3C www-style mailing list <www-style@w3.org>
> -----Original Message-----
> From: Tab Atkins Jr. [mailto:jackalmage@gmail.com]
> Sent: Friday, March 13, 2015 4:51 PM
>
> Yay list-style-position interop bugs! They're the absolute worst, everyone's
> terrible, they made me very sad when I investigated them in depth. :(
>
> The correct behavior is that list-style-position:inside makes the ::marker
> pseudo an ordinary position:static element. By default, it's a display:inilne
> immediately preceding the ::before pseudo. The behavior of blocks inside
> the list item should then fall out in the obvious fashion - the marker, being
> inline content, gets wrapped in an anonymous block before the block
> element.
>
> In other words, the *correct* behavior (in terms of being sensible and
> matching the spec) is for your example to render exactly the same as:
>
> <div class='ul'>
> <div class='li'><p>Text</p>
> </div>
> <style>
> div.li::before { content: "\2022"; }
> </style>
Thanks Tab, from your example and description IE/Firefox are pretty much doing the correct thing here (looking at modified original sample http://jsfiddle.net/ne1pfneh/1/), which is supported by CSS test I've linked earlier.
I'll follow up with Chromium bug then.
Received on Tuesday, 17 March 2015 19:53:34 UTC