Re: [whatwg] What it means for attributes of input to apply or not apply

2012-01-12 Thread Ian Hickson
On Wed, 22 Jun 2011, Edward O'Connor wrote: When adding the placeholder= attribute to input type=number, one of our engineers asked me about the behavior of content attributes that don't apply to certain input types. Consider for example input type=range. The spec says [t]he following

[whatwg] What it means for attributes of input to apply or not apply

2011-06-22 Thread Edward O'Connor
Hi, When adding[1] the placeholder= attribute to input type=number, one of our engineers asked me about the behavior of content attributes that don't apply to certain input types. Consider for example input type=range. The spec says[2] [t]he following content attributes *must not be specified*

Re: [whatwg] What it means for attributes of input to apply or not apply

2011-06-22 Thread Aryeh Gregor
On Wed, Jun 22, 2011 at 11:50 AM, Edward O'Connor eocon...@apple.com wrote: The second bit (does not apply to the element), however, isn't clear. Is it a UA conformance requirement? What does it mean? I *think* it means that the placeholder= attribute has no effect on the rendering of input

Re: [whatwg] What it means for attributes of input to apply or not apply

2011-06-22 Thread Ian Hickson
On Wed, 22 Jun 2011, Edward O'Connor wrote: The second bit (does not apply to the element), however, isn't clear. It's a hook used here: http://www.whatwg.org/specs/web-apps/current-work/complete.html#common-input-element-attributes I'll add a hyperlink or something to make it clearer.