- From: Rune Lillesveen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Aug 2024 12:18:10 +0000
- To: public-css-archive@w3.org
> 1. Note that the current spec uses [::nth-fragment](https://drafts.csswg.org/css-overflow-5/#selectordef-nth-fragment), however having a single element [inherit different styles per fragment](https://drafts.csswg.org/css-overflow-5/#selectordef-nth-fragment:~:text=This%20means%20that%20elements%20split%20between%20fragment%20boxes%20may%20have%20different%20styles%20for%20different%20parts%20of%20the%20element) introduces significant implementation complexity. As such, we would propose initially resolving to go with a single ::fragment style (i.e. the syntax mentioned in the [inline issue](https://drafts.csswg.org/css-overflow-5/#issue-978c73c1)) [↩](#user-content-fnref-1-ebc26bcde0bfad8bbc5de65798fe150b) That would be pretty similar to `::first-line`, yes. For the single `::fragment` case, would you then do inheritance from `::fragment` into the elements laid out into fragments at style recalc time, reflected in getComputedStyle(), or keep a separate set of styles for layout like is done for `::first-line`? -- GitHub Notification of comment by lilles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10715#issuecomment-2277818002 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 August 2024 12:18:11 UTC