- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Sat, 5 Dec 2015 17:10:18 -0800
- To: Alan Stearns <stearns@adobe.com>
- Cc: "www-style@w3.org Style" <www-style@w3.org>, "rob.buis@samsung.com" <rob.buis@samsung.com>, "Eric A. Meyer" <eric@meyerweb.com>
On Sat, Dec 5, 2015 at 10:18 AM, Alan Stearns <stearns@adobe.com> wrote: > In a bug [1], it’s noted that the ellipse() function is defined to only accept 0 or 2 radius values. If one radius is provided, it’s an invalid shape function. Tab suggested in the bug that we allow a 1-radius ellipse, and just set the second radius to the same as the first. > > > > As I recall [2], I defined the ellipse function to match what we have in radial-gradient(), where if an ellipse ending-shape is explicitly used, you can only use 0 or 2 radius values. > > I don’t much care whether we allow one-radius ellipse syntax or not, but if we do I think we should also change radial-gradient() to match. I don’t think it’s terribly useful to have a one-radius ellipse that devolves to a circle, though. So I’m slightly inclined against the change because I don’t think the limited use warrants mucking around with gradients. Check radial-gradient() again - it requires 0 or 2 *length/percentage* values, or 1 keyword. You have ellipse() accepting 0 or 2 keywords (along with 0 or 2 len/%). You're not currently matching radial-gradient() at all. ^_^ ~TJ
Received on Sunday, 6 December 2015 01:11:06 UTC