Open Bug 1506241 (margin-trim) Opened 6 years ago Updated 3 months ago

Implement the margin-trim property from CSS Box Level 4

Categories

(Core :: Layout, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: svoisen, Unassigned)

References

(Blocks 2 open bugs, )

Details

(Keywords: dev-doc-needed, parity-safari)

Attachments

(1 file)

36 bytes, text/x-github-pull-request
Details | Review
Tracking bug to consider future implementation of https://drafts.csswg.org/css-box-3/#margin-trim

The margin-trim property allows for trimming margins of children where they adjoin a container's edges.
Priority: -- → P3
Blocks: css-box-4
Attached file MDN: Data update
Alias: margin-trim
Keywords: dev-doc-needed
Summary: Implement the margin-trim property from CSS Box Level 3 → Implement the margin-trim property from CSS Box Level 4

Any news on this?
2 years since this became a recommendation.
https://www.w3.org/TR/css-box-4/#propdef-margin-trim

(In reply to serradeil from comment #3)

2 years since this became a recommendation.
https://www.w3.org/TR/css-box-4/#propdef-margin-trim

Note that the specification is not a recommendation yet but a "first public working draft", which normally means it is still many years away from becoming a recommendation. Even the previous specification CSS Box Model Module Level 3 is not yet a recommentation.
Regarding margin-trim, there are currently still three issues open in the specification, https://github.com/w3c/csswg-drafts/issues/3314, https://github.com/w3c/csswg-drafts/issues/6922 and https://github.com/w3c/csswg-drafts/issues/3256, so its definition is still incomplete.

And the date of the specification is just the one of the newest version of it which normally updates relatively regularily.

With all that said, I would love to see this being implemented pretty soon as it covers a very common use case. One way to push this is to mention it in the State of CSS 2022 survey which will happen pretty soon.

Sebastian

See Also: → 1789316

Note that the specification is not a recommendation yet ... Even the previous specification is not yet a recommendation.

thanks.
Just curious: "TR" once used to mean "technical recommendation", meaning "it's done for now and official", unlike "WD" (working draft) or "CR" (candidate recommendation).

I understand the meaning of publications on csswg.org, but when did unfinished specification become published under a W3C TR address? That's not helpful to understand and follow the current state of CSS modules, hence my notion "this became a recommendation"

Thank you and will check with the 22 survey!!

(In reply to serradeil from comment #5)

Just curious: "TR" once used to mean "technical recommendation"

TR actually stands for "Technical Report", not Recommendation. The maturity levels like WD and CR are a different thing.

I understand the meaning of publications on csswg.org, but when did unfinished specification become published under a W3C TR address?
That's not helpful to understand and follow the current state of CSS modules, hence my notion "this became a recommendation"

The maturity level can be seen at the left side of any specification. You can also see the status of all CSS specifications under https://www.w3.org/Style/CSS/current-work.

But now enough side-tracking of this issue. Further discussions should be held privately or in the CSSWG.

Sebastian

Severity: normal → S3

Adding a reference to the webkit bug, which is https://bugs.webkit.org/show_bug.cgi?id=245598

(They're also adding tests for this feature to WPT in https://github.com/web-platform-tests/wpt/pull/38019 )

For what it's worth, Safari shipped margin-trim in 16.4.

Also, the related Chromium bug is https://bugs.chromium.org/p/chromium/issues/detail?id=1405835.

Sebastian

Keywords: parity-safari
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: