W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > November 2019

[fxtf-drafts] [motion-1] A proposal to split motion path into 2 levels (#384)

From: Boris Chiou via GitHub <sysbot+gh@w3.org>
Date: Tue, 19 Nov 2019 21:36:47 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issues.opened-525282192-1574199406-sysbot+gh@w3.org>
BorisChiou has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [motion-1] A proposal to split motion path into 2 levels ==
This proposal is from the discussion with @dirkschulze in dev-platform (lists.mozilla.org):

> For the spec it might make sense to split into 2 levels: Level 1 could be the 3 longhand properties offset-path (with the limitations you mentioned), offset-distance and offset-rotate and the shorthand offset. Level 2 would include the 2 remaining properties and the ray() and basic shape functions. If 2 implementations support the 3 longhand properties consistently it brings the spec of level 1 to CR faster.

In other words:
* [motion-1]
  1. `offset-path: none | path()`
  2. `offset-distance`
  3. `offset-rotate`
  4. `offset` shorthand
  5. ... and other basic information
* [motion-2]
  1. `offset-path: ray() | <url> | [ <basic-shape> || <geometry-box> ]`
  2. `offset-anchor`
  3. `offset-position`

Blink has shipped all properties and values defined in [motion-1] above, and Gecko is ready to ship them. Dirk is working on the basic properties in [Webkit Bug 203847](https://bugs.webkit.org/show_bug.cgi?id=203847). So I believe these three layout engines support the basic properties soon, and it would be easier to bring [motion-1] to CR.
(Note: I believe ray() is not ready at least for now, because of https://github.com/w3c/fxtf-drafts/issues/369).

cc @ericwilligers 

Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/384 using your GitHub account
Received on Tuesday, 19 November 2019 21:36:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:26 UTC