- From: James via GitHub <sysbot+gh@w3.org>
- Date: Sun, 06 Aug 2023 21:12:39 +0000
- To: public-fxtf-archive@w3.org
Bumping this, as I came across it in in https://github.com/web-platform-tests/wpt/pull/41279, https://github.com/mdn/content/pull/28157, https://github.com/mdn/browser-compat-data/pull/20461 and https://github.com/mdn/data/issues/678. According to https://github.com/w3c/fxtf-drafts/issues/5 and more recent testing browsers don't support margin-box on mask-origin and mask-clip, despite it still being a property of `<geometry-box>`, and don't plan to (especially given their support for its removal from wpts) I suggest changing `<geometry-box>` to `<coord-box>`, which has the correct properties > `content-box | padding-box | border-box | fill-box | stroke-box | view-box` offset-path changed from using <geometry-box> to <coord-box> between the [2018 working draft](https://www.w3.org/TR/motion-1/#offset-path-property) and the [2021 editor's draft](https://drafts.fxtf.org/motion-1/#offset-path-property) ([relevent commit](https://github.com/w3c/fxtf-drafts/commit/b0cc95afd8c874aaddb15e99339bd7c7d47ffea3)), presumably for similar reasons, which gave me the idea of doing it for mask-origin and mask-clip as well. -- GitHub Notification of comment by FormularSumo Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/439#issuecomment-1666968971 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 6 August 2023 21:12:42 UTC