- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Aug 2020 07:27:44 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-inline-3] leading-trim accumulation == We allow ancestors to affect leading trimming on descendants, so that common cases like ``` <div class=warning style="borders and padding and leading-trim"> <p>This is just a paragraph. Maybe this line is <p>, or not, it could be anything. </div> ``` will work for authors. But we don't specify what happens if various ancestors have different values for `leading-trim`. Maybe we should do something similar to `break-before` and switch to an auto/no/yes model where auto does whatever the ancestor says and otherwise the innermost value wins? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5426 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 August 2020 07:27:46 UTC