Re: [csswg-drafts] [css-shapes-1] ellipse() grammar gratuitously inconsistent with radial-gradient() (#824)

I should have addressed this a few years ago. Sorry for the delay.

Adding the *-corner keywords should be fine.

My guess is it's still possible to change the `ellipse()` syntax to exactly match radial gradients. If we do that, there will be some breakage. It would be limited to instances of `ellipse()` where two keywords are used (which is likely very small), and the breakage would be limited to having someone's `shape-outside` or `clip-path` no longer apply (both have okay fallbacks).

BUT I think we could change `ellipse()` to allow either what's currently specified OR something matching a current radial gradient:

`<extent-keyword> | [ <extent-keyword> | <length-percentage> ]{2}?`

Then there would be no breakage, no one would get a surprise trying to copy a radial gradient ellipse into an `ellipse()`, we would get the two-keyword case (which is useful for creating ellipses that are the largest that can fit in a reference box), and we could decide whether to extend the radial gradient syntax to match (fully containing the ellipse is less useful there, but still could be good)

-- 
GitHub Notification of comment by astearns
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/824#issuecomment-546097364 using your GitHub account

Received on Thursday, 24 October 2019 20:50:16 UTC