NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 1008 - input@inputmode
input@inputmode
Status: RESOLVED DUPLICATE of bug 998
Product: Validator.nu
Classification: Unclassified
Component: General
HEAD
All All
: P2 major
Assigned To: Nobody
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-04 13:52 CET by Andy R
Modified: 2014-11-05 13:44 CET (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy R 2014-11-04 13:52:57 CET
This is another bug which was reported almost 1 year ago, and it seems that nobody took it seriously.
When setting @inputmode on textarea, the validator flags it as incorrect stating this confusing explanation:
Attribute inputmode not allowed on element textarea at this point.
Attributes for element textarea:
Global attributes
autocomplete
autofocus
cols
dirname
disabled
form
inputmode
maxlength
name
placeholder
readonly
required
rows
wrap
Moreover, on input elements this attribute is neither allowed nor listed in the allowed attributes, although it is in the specs.
While I understand that @inputmode is a problem because it is in the 5.1 version of the spec and it has been only recently inserted in the html5 version (without proper explanation), the Validator should assume either consider it wrong or accept it, possibly warning the author about the lack of implementation for such an attribute.
Either keep @inputmode not allowed, and erase it from the list of allowed attributes, or make it allowed. This issue seems fairly serious.
Comment 1 Michael[tm] Smith 2014-11-05 04:01:40 CET
(In reply to Andy R from comment #0)
> This is another bug which was reported almost 1 year ago, and it seems that nobody took it seriously.

If there's a bug already open on this, then we're aware of it and there's no need to open a new bug for it. It's not a matter of it not being taken seriously, it's just a matter of priorities and time constraints.
Comment 2 Andy R 2014-11-05 13:44:54 CET

*** This bug has been marked as a duplicate of bug 998 ***