[
https://issues.apache.org/jira/browse/TAP5-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183516#comment-14183516
]
Howard M. Lewis Ship commented on TAP5-2400:
--------------------------------------------
I'm not sure what the action for this is, I don't understand the issue. What
would you propose as the right way to capture the key or character typed by the
user in a cross-framework, cross-browser way?
> EventWrapper's "key" and "char" properties are broken
> ------------------------------------------------------
>
> Key: TAP5-2400
> URL: https://issues.apache.org/jira/browse/TAP5-2400
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Felix Scheffer
>
> The EventWrapper copies the properties "key" and "char" from the native
> event but KeyboardEvent has neither a "key" nor a "char" property in Chromium.
> According to https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent
> "char" is only supported by the IE and "has been dropped from DOM Level 3
> Events".
> According to
> https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent.key neither
> Chrome nor Opera nor Webkit supports the "key" property at the moment
> I think "char" should be removed from the EventWrapper and there should be a
> fallback solution using "keyCode" when the browser does not support "key"
> There is a proposal for a "code" property but it's still a working draft:
> https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent.code
> I checked with Prototype and jQuery but there are no real differences. jQuery
> wraps the native event with jQuery.Event but the actual values for these
> properties are the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
