W3C home > Mailing lists > Public > www-style@w3.org > November 2013

Re: [css-shapes] <basic-shapes> etc. summary 3

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sun, 10 Nov 2013 17:20:44 -0800
Message-ID: <CAAWBYDC_Eqe1VV+vO0kRmUBDvE03mZem0ifS=xRO8Tif80yXUQ@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: www-style list <www-style@w3.org>
On Sun, Nov 10, 2013 at 4:58 PM, Alan Stearns <stearns@adobe.com> wrote:
> On 11/10/13 3:07 PM, "Alan Stearns" <stearns@adobe.com> wrote:
>>We change circle() and ellipse() to use radial gradient syntax:
>>circle() = circle( [<size>] [at <position>] )
>>ellipse() = ellipse( [<size>] [at <position>] )
> Now that I'm starting to make these changes, I'm noticing that <size> as
> defined by radial gradients does not allow percentages for circle radii,
> and the corner keywords there are more suited for gradients than shapes
> (farthest and closest corner radii will not tend to produce useful circles
> for shape-outside or clip-path).
> I think I'd like to amend this to:
> circle() = circle( [<shape-radius>] [at <position>] )
> ellipse() = ellipse( [<shape-radius>{2}] [at <position>] )
> Where <shape-radius> keeps the same width/height/cover/contain keywords as
> the current shapes draft, and we keep the same percentage circle radius
> definition in the draft.

Alternately, we could just define <percentage> circle radius for
radial gradients the same way, and add the 'width' and 'height'

circle()'s use of "cover" isn't correct - it's different from the
definition of "cover" in every other instance of the term in CSS, or
any reasonable English definition, as it doesn't "cover" anything.
However, I'm not sure of what a better keyword would be.

For that matter, its definition of "contain" is different from every
other instance, too - it only matches the normal meaning if the circle
is centered.  Any other time, the circle won't actually be contained
in the shape.

If these are really the definitions you want, I suggest the keywords
"max" and "min" (similar to the usage of the words in the vmin and
vmax keywords), and keep around the full set of radial-gradient
keywords, so authors can still use "contain" and "farthest-side" too.

Received on Monday, 11 November 2013 01:21:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:36 UTC