Update transform-box initial & fallback values to match latest CSS WG resolution

NEW
Unassigned

Status

()

Core
Layout
P3
normal
a year ago
9 months ago

People

(Reporter: Amelia Bellamy-Royds, Unassigned)

Tracking

53 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a year ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce:

In Firefox 55, the transform-box property is implemented according to the spec as it existed a couple months ago.  Implementation shipped as described in issue #1208550



Actual results:

In the process of getting other browsers support, some issues with the current spec were identified.  The CSS WG resolved to change the initial value of the property and the way that the CSS box layout values map to SVG layout values (and vice versa).

See summary here: https://github.com/w3c/csswg-drafts/issues/857#issuecomment-296074806

Blink and WebKit are working on implementations based on the latest resolutions:
- Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=595829
- WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=145783


Expected results:

The following changes affect the Firefox implementation:

- The initial value is now `view-box`
- The used values change when a CSS box keyword is used for an element without CSS layout boxes, or when an SVG box keyword is used for an element without SVG layout.  The correspondences are those defined in the draft Fill & Stroke module for the fill-origin property: https://drafts.fxtf.org/fill-stroke-3/#fill-origin
Blocks: 1208550
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

a year ago
Priority: -- → P3

Updated

11 months ago
Assignee: nobody → cku

Updated

9 months ago
Assignee: cku → nobody
You need to log in before you can comment on or make changes to this bug.