This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html Section: http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element-0 Comment: Add textarea { resize: both; } Posted from: 91.181.81.47 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b10pre) Gecko/20110216 Firefox/4.0b10pre
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: That's up to the UA's 'textarea' binding.
What does that mean?
This section defines the behaviour and presentation of a 'textarea' element in terms of a hypothetical BECSS binding: http://www.whatwg.org/specs/web-apps/current-work/complete.html#the-textarea-element-0 How that binding works, including whether it allows you to pop the editor into its own window, whether it has particular borders or 'resize' values, whether it does spelling checking, whether it has a built in thesaurus, whether it can write "tl;dr" summaries for you, whether it does syntax highlighting, whether it supports dictation via speech recognition, etc, etc, etc, is all up to the UA.
mass-moved component to LC1