W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2018

[csswg-drafts] [css-box-3][css-break-4] Do terms like "truncate", "discard" and "trim" require more specification? (margin-break/margin-trim) (#3443)

From: Bernhard Fey via GitHub <sysbot+gh@w3.org>
Date: Fri, 14 Dec 2018 16:35:32 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-391181775-1544805331-sysbot+gh@w3.org>
bernhardf-ro has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-box-3][css-break-4] Do terms like "truncate", "discard" and "trim" require more specification? (margin-break/margin-trim) ==
- "are **discard**ed or kept"
- "are **trim**med"
- "are **truncate**d"
- "are **truncate**d _to zero_"
- ("**truncate** _to the remaining fragmentainer extent_")

I wonder if such property definitions should either specify the behavior in more detail before using those terms or define the terms somewhere. To me and my colleagues they are not entirely clear. I have collected some of our points of confusion:

1. Does "_truncate_" without a target mean "_truncate to zero_"?
2. Does "_truncate to X_" mean "_set value to X_" or "_set value to X if it is larger than X_" (so "_truncate to zero_" would not change negative values)?
3. Same as 1. and 2. but for "_trim_"
4. Does "_discard_" mean "_set value to zero_" (in contrast to things like "skip any processing that requires the value and do some special alternative steps...")?
5. If those change the value, can we assume it is the _used value_ (e.g. of margin-top) that is changed, not affecting inheriting children but the resolved style for `getComputedStyle`?

Any clarification, here or in the specifications, would be appreciated.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3443 using your GitHub account
Received on Friday, 14 December 2018 16:35:34 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:41 UTC