Yes, CSS3 naming is easier to understand.
And like other border-* properties, top, right, bottom, left should be
mapped to equivalent FO directions in lr-tb mode (respectively before,
end, after, start).

2012/10/12 Clay Leeds <>:
> I would prefer CSS3 naming conventions as well.
> Clay
> "My religion is simple. My religion is kindness."
> - HH The Dalai Lama of Tibet
> On Oct 12, 2012, at 6:48 AM, Peter Hancock <> wrote:
>> Thanks for taking the time to review this!
>> On Fri, Oct 12, 2012 at 2:12 PM, Glenn Adams <> 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


Reply via email to