This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19899 - Support for Break characters should be reconsidered for Textarea
Summary: Support for Break characters should be reconsidered for Textarea
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Erika Doyle Navara
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/common-i...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-07 21:11 UTC by James Cockin
Modified: 2016-04-21 15:10 UTC (History)
6 users (show)

See Also:


Attachments

Description James Cockin 2012-11-07 21:11:32 UTC
The specification currently states that the attribute, if specified, must have a value that contains no "LF" (U+000A) or "CR" (U+000D) characters.

I would like to request that this restricition is reconsidered for Textarea input fields which, by their nature, are designed to span multiple lines and a placeholder hint to show a user an example of the data to enter should also be able to span multiple lines.

An example of this requirement is where a textarea is used to create a list of items e.g.

Please enter areas of work:
    Area A
    Area B
    Area C

The specification suggests the alternative use of Title but in most browsers this does not display in as helpful a manner and is, anyway, currently discouraged by the W3C, see:

http://dev.w3.org/html5/spec/global-attributes.html#attr-title
Relying on the title attribute is currently discouraged as many user agents do not expose the attribute in an accessible manner as required by this specification 

The use of this feature is becoming increasingly common, there is a clear demand for this feature to be supported (as can be seen by a quick Google search) and the decision to disallow line breaks imposes a decision that should really be left to individual website developers as to what best suits their own requirements.
Comment 1 Travis Leithead [MSFT] 2016-04-21 15:10:00 UTC
HTML5.1 Bugzilla Bug Triage: Moved to GitHub: https://github.com/w3c/html/issues/234

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!