- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Mar 2019 04:30:43 +0000
- To: public-css-archive@w3.org
@fantasai we've implemented it by following the same code path as for `::before/::after` in box construction / layout (when `content` is specified). We've added a few tweaks for `list-style-position:outside` to make it compatible with our old layout that we should specify (in css-lists). We haven't implemented `position:marker` at all and I believe it wouldn't be web-compatible as currently [specified](https://drafts.csswg.org/css-lists/#position-marker) because "counts as absolutely positioned" would give it the wrong stacking level for painting. We also haven't implemented the `marker-side` property (yet). I'll file a separate spec issue with the details on how we do layout for `outside`. Layout for `inside` should work pretty much exactly as for `::before/::after`. If `content` isn't specified, then we still use our legacy layout code (aka nsBulletFrame). We've only updated it to use the new `list-item` counter and use `::marker` styles. My goal for the future is to generate a content node from `list-style-type` etc and then use the same layout code for everything (and then remove nsBulletFrame). I don't think you need to block this on layout details for `list-style-position:outside` since that's under-specified anyway at the moment and the tweaks we added are fairly minor and not really related to the `content` property per se. -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3499#issuecomment-476969268 using your GitHub account
Received on Wednesday, 27 March 2019 04:30:45 UTC