[csswg-drafts] [css-shapes] Should `circle()` serialization omit the `center` value? (#10645)

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

== [css-shapes] Should `circle()` serialization omit the `center` value? ==
In [CSS Basic Shapes 1](https://drafts.csswg.org/css-shapes/#funcdef-basic-shape-circle), the serialization section says that `at center` can be omitted from `circle()` and `ellispse()` since it's the default value.

However, in [Motion Path Level 1](https://drafts.fxtf.org/motion/#offset-path-property) we see this text:

> For all [`<basic-shape>`](https://drafts.csswg.org/css-shapes-1/#typedef-basic-shape)s, if they accept an at `<position>` argument but that argument is omitted, and the element defines an [offset starting position](https://drafts.fxtf.org/motion/#offset-starting-position) via [offset-position](https://drafts.fxtf.org/motion/#propdef-offset-position), it uses the specified offset starting position for that argument. Otherwise it defaults as specified for each function.

This means that in Motion Path, `circle(20px)` and `circle(20px at center)` mean different things in Motion Path.

This would require that we should either have different serialization rules for some Basic Shapes depending on the property they are used in, or we modify the serialization rules to *not* omit the center value.


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


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

Received on Wednesday, 31 July 2024 00:17:07 UTC