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 23318 - @inputmode in textarea
Summary: @inputmode in textarea
Status: NEW
Alias: None
Product: HTML Checker
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-22 00:52 UTC by Andrea Rendine
Modified: 2014-02-24 00:13 UTC (History)
1 user (show)

See Also:


Attachments

Description Andrea Rendine 2013-09-22 00:52:38 UTC
Tested some HTML5-new attributes for form controls. On <textarea> @inputmode is correctly flagged as "not allowed on HTML element input", as it has apparently been removed from official spec, but it is still present in the available attributes, generating confusion.
Comment 1 Andrea Rendine 2014-02-24 00:13:54 UTC
After several months this small bug is still present. @inputmode is flagged as "not allowed" both in <input> and in <textarea>. But in the latter, it is also listed among the allowed attributes. Now everything depends on the normative source. If it is HTML5 CR, then the attribute is invalid and it's right not to show it as allowed. Otherwise if you validate against HTML5.1 WD or the nightly editor's draft, then it's valid in both elements and must not be flagged. Everything is accepted but the actual situation is confusing.

Attribute inputmode not allowed on element textarea at this point.
<body>↩<p><textarea inputmode="latin"></text
Attributes for element textarea:
Global attributes
autocomplete
autofocus
cols
dirname
disabled
 *inputmode*
maxlength
name
placeholder
readonly
required
rows
wrap