[fxtf-drafts] [motion-1] offset-position + circle() (#504)

tabatkins has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [motion-1] offset-position + circle() ==
In [the definition of `<basic-shape>` for 'offset-path'](https://drafts.fxtf.org/motion-1/#offset-path-property), there's a paragraph that states:

> If a circle or ellipse basic shape has no explicit center position, the shape is centered at the [=initial position=] of the path, as described in 'offset-position'.

This contradicts [Shapes 1](https://drafts.csswg.org/css-shapes-1/#funcdef-basic-shape-circle), which simply defaults an omitted center-position to "center" without making it configurable.

Worse, this means that 'offset-position' now does *two completely unrelated things* - for ray(), it sets where the ray emerges from (aka where `offset-distance: 0%` places you), but for circle() and ellipse() it (sometimes!) sets the *center* of the ellipse, which is *not* a point on the path at all.

I don't understand why this is necessary; you can just set the center position directly in the function if you need to, and if you omit it I think it's *confusing* for it not to act like an omitted position in other contexts. To get the default behavior that Shapes defines I have to explicitly say `circle(... at center)`.

Can we just drop this odd behavior and have circle()/ellipse() default their center position as normal?

Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/504 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 3 March 2023 23:22:07 UTC