Re: [whatwg] textarea semantics for wrap, readonly, and disabled

2009-09-04 Thread Ian Hickson
On Wed, 2 Sep 2009, Dirk Pranke wrote: In testing various combinations of attributes on textareas, I've found a couple of inconsistencies and some vagueness in the spec. 1) The wrap=hard attribute appears to be defined such that you get hard line breaks at the specified character width

Re: [whatwg] textarea semantics for wrap, readonly, and disabled

2009-09-03 Thread Anne van Kesteren
On Wed, 02 Sep 2009 22:26:53 +0200, Dirk Pranke dpra...@chromium.org wrote: 1) ... I'll let someone else address this one. 2) wrap=off does not appear to be a legitimate value, despite being implemented in all the major browsers. Is this an oversight, or an intentional omission? It is

[whatwg] textarea semantics for wrap, readonly, and disabled

2009-09-02 Thread Dirk Pranke
Hi all, In testing various combinations of attributes on textareas, I've found a couple of inconsistencies and some vagueness in the spec. 1) The wrap=hard attribute appears to be defined such that you get hard line breaks at the specified character width of the element, but the semantics of the

Re: [whatwg] textarea semantics for wrap, readonly, and disabled

2009-09-02 Thread Tab Atkins Jr.
On Wed, Sep 2, 2009 at 3:26 PM, Dirk Prankedpra...@chromium.org wrote: 2) wrap=off does not appear to be a legitimate value, despite being implemented in all the major browsers. Is this an oversight, or an intentional omission? This value is specified down in the rendering section, as it

Re: [whatwg] textarea semantics for wrap, readonly, and disabled

2009-09-02 Thread Dirk Pranke
On Wed, Sep 2, 2009 at 1:33 PM, Tab Atkins Jr.jackalm...@gmail.com wrote: On Wed, Sep 2, 2009 at 3:26 PM, Dirk Prankedpra...@chromium.org wrote: 2) wrap=off does not appear to be a legitimate value, despite being implemented in all the major browsers. Is this an oversight, or an intentional