A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/w3c/csswg-drafts/issues/5426 below:

[css-inline-3] text-box-trim accumulation · Issue #5426 · w3c/csswg-drafts · GitHub

Skip to content Navigation Menu

Saved searches Use saved searches to filter your results more quickly

Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Additional navigation options

[css-inline-3] text-box-trim accumulation #5426

Description

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?

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3