[whatwg] [wf2] :read-write pseudoclass description issue
Rikkert Koppes
lists at rikkertkoppes.com
Wed Feb 11 02:22:14 PST 2009
I see your point, to go for another route, maybe you'd just edit the
source of the problem (the note), remove it and include a text similar
to the remark about the disabled attribute. I.e:
-------
When an input element is disabled, it is immutable.
When an input element is readonly, it is immutable.
-------
However, there is no readonly concept defined (maybe this will clarify
more, but actually I think it's likely to complicate things even more).
Hence, another suggestion could be:
-------
An input element to which the readonly attribute applies and has that
attribute specified, is immutable.
-------
Cheers,
Rikkert Koppes
Ian Hickson wrote:
> On Wed, 11 Feb 2009, Rikkert Koppes wrote:
>
>> At [1] I'd suggest changing the second sentence to "When specified and
>> applicable, the element is immutable".
>>
>> [1]: http://www.whatwg.org/specs/web-apps/current-work/#attr-input-readonly
>>
>
> Yeah, I keep thinking of doing something like that. The reason I haven't
> yet is that I don't want to go down the route of people seeing that and
> thinking that that means that other things in that section might apply
> even when they don't (the intro to that section explicitly says that
> nothing there applies if the attributes aren't applicable).
>
>
More information about the whatwg
mailing list