My preference would be to provide both the CSS3 named properties and also writing system relative properties, giving the user the preference of which to use. But I would suggest using the same pattern as CSS3 for property names for these latter:
border-top-left-radius border-top-right-radius border-bottom-right-radius border-bottom-left-radius border-before-start-radius border-before-end-radius border-after-start-radius border-after-end-radius it would also be useful to support the border-radius shortcut from CSS3 (mapping to the above CSS3 longhand flavors) On Fri, Oct 12, 2012 at 8:48 PM, Peter Hancock <[email protected]>wrote: > Thanks for taking the time to review this! > > On Fri, Oct 12, 2012 at 2:12 PM, Glenn Adams <[email protected]> wrote: > >... > > However, I also notice that the fox property name proposed in [1] > contains > > uppercase (fox:border-BLOCK-radius-INLINE). That is a definite no-no, and > > thus warrants a -1 vote until changed to LC. All LC please! > > The upper case BLOCK and INLINE were meant to represent variables with > values before and after, and start and end, respectively. > > > I haven't had a chance to look at the details, but does this extension > > follow the (property name and value) definitions found in CSS3 > Backgrounds > > and Borders [4]? If it doesn't, then my vote is -1; otherwise, I would > vote > > +1. > > I do concede that there is a departure from CSS3: > To specify the top left corner in CSS3 you do > border-top-left-radius="x y" > and with the fox extension (assuming a viewport orientated with the page) > fox:border-start-radius-before="x" > fox:border-before-radius-start="y" > > If this is unsatisfactory then I guess it is back to the drawing board. > > Peter >
