W3C home > Mailing lists > Public > www-style@w3.org > February 2014

Re: [css-counter-styles] potential abuse of pad

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 24 Feb 2014 17:34:46 -0800
Message-ID: <CAAWBYDBPj7WdXELVtCr7r_dBfQ_J2Yd9Ka+EADaJ_ehcA5Vkrg@mail.gmail.com>
To: Xidorn Quan <quanxunzhen@gmail.com>
Cc: www-style list <www-style@w3.org>
On Mon, Feb 24, 2014 at 5:31 PM, Xidorn Quan <quanxunzhen@gmail.com> wrote:
> On Tue, Feb 25, 2014 at 12:27 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> On Fri, Feb 21, 2014 at 9:28 PM, Xidorn Quan <quanxunzhen@gmail.com> wrote:
>>> Hi,
>>>
>>> The spec mentions the potential abuse of some systems. However, it is
>>> also possible for 'pad' to be abused in a similar way. The total
>>> characters produced by pad should be limited as well.
>>>
>>> Nevertheless, I'm not sure what should happen for a too long pad.
>>> There are two options:
>>>
>>> 1. drop the whole representation, and use the fallback;
>>> 2. drop symbols until the total length is acceptable.
>>>
>>> Personally I prefer the first option though I do not have a strong reason.
>>
>> Nope, 'pad' isn't abusable.  It produces representations that don't
>> depend on the value of the counter, and so is safe.
>>
>> That is, I'm fine if you can generate a gig of counter representation
>> by specifying a gig of descriptor in your stylesheet.  I'm not fine if
>> you can generate a gig of representation from less than a kilo of
>> stylesheet.
>>
>> 'pad' is basically equivalent in abuse potential to 'content':
>> "*::before { content: "[long string here]"; }" is basically the same
>> thing.
>
> What about
>
> @counter-style { pad: 1000000000 "0"; }

Oh, hrm, you're right.  Okay, I'll add something.

~TJ
Received on Tuesday, 25 February 2014 01:35:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 25 February 2014 01:35:36 UTC