Contact emails
mste...@chromium.orgSpecification
https://drafts.csswg.org/css-box-4/#margin-trimSummary
The `margin-trim` CSS property may be used to omit margins before or after the first or last child of a container. This is supported on regular block containers and multicol containers. Note: A previous version of the spec also applied this for flex and grid containers, but this has been removed. https://drafts.csswg.org/css-box-4/#margin-trim This is somewhat similar to the effect caused by the margin quirk that is applied to P, H1, H2... elements inside BODY and table cell elements (in quirks mode), but more powerful, generic, and expressive.Blink component
Blink>LayoutWeb Feature ID
margin-trimMotivation
No information providedInitial public proposal
No information providedTAG review
No information providedTAG review status
Not applicableGoals for experimentation
NoneRisks
Interoperability and Compatibility
No information providedGecko: Positive (
https://bugzilla.mozilla.org/show_bug.cgi?id=1506241) Mozilla are actively working on implementing this feature.
WebKit: Shipped/Shipping (
https://webkit.org/blog/16854/margin-trim)
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No information providedDebuggability
No information providedWill this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
YesYeshttps://wpt.fyi/results/css/css-box/margin-trim?label=experimental&label=master&alignedFlag name on about://flags
No information providedFinch feature name
MarginTrimRollout plan
Will ship enabled for all usersRequires code in //chrome?
FalseTracking bug
https://issues.chromium.org/issues/40886857Estimated milestones
| Shipping on desktop | 155 |
| Shipping on Android | 155 |
| Shipping on WebView | 155 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No information providedLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5197863732772864?gate=6474161734156288Links to previous Intent discussions
Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKWZFm4REgNxwYFjJTZw-fUnxc1NGk2naOevLZCzOqLdL8eQBw%40mail.gmail.com