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 23886 - Needs to define key value when dead key is pressed twice
Summary: Needs to define key value when dead key is pressed twice
Status: RESOLVED WORKSFORME
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Gary Kacmarcik
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-22 06:28 UTC by Masayuki Nakano
Modified: 2014-04-22 00:26 UTC (History)
3 users (show)

See Also:

Attachments

Description Masayuki Nakano 2013-11-22 06:28:39 UTC 
On Windows, e.g., dead key "`" is pressed twice, "``" is inputted at second keypress.

Then, what value is set to the .key of second keydown/keyup event, "``" or "`"?

The first key event causes combining character value for .key values. And if dead key is succeeded to input a character, the combined character is set to .key.

Therefore, I think that "``" is consistent result.
Comment 1 Masayuki Nakano 2013-11-22 07:17:09 UTC 
Oh, but example 30 defines strange case. On Windows, this key sequence should cause "^q". We need an example of this case for compatibility between browsers on Windows.
Comment 2 Gary Kacmarcik 2014-02-19 00:45:38 UTC 
This is example #34 (the second example in section "6.4.3 Dead keys") of the current draft.
Comment 3 Travis Leithead [MSFT] 2014-04-22 00:26:24 UTC 
(In reply to Gary Kacmarcik from comment #2)
> This is example #34 (the second example in section "6.4.3 Dead keys") of the
> current draft.

I think that resolves this bug. Please reactivate if you believe otherwise.