[Bug 26019] No way to initialize modifier states except "Alt", "Control", "Shift" and "Meta" at constructing DOM event with constructor

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26019

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(In reply to Masayuki Nakano from comment #2)
> Yeah, if they can be initialized with constructor, it's the best.

I've got a private copy of this change now, and while writing it I made a few
assumptions that I'd like to discuss:

1. Some of the getModifierState params duplicate existing attributes, e.g.,
"Alt" and the altKey IDL attribute. Consequently, I've not created the new
initializers for "Alt", but have made it explicit (in the prose for the
existing "altKey" initializer on the dictionary) that is also sets the internal
modifier state of the event such that calls to getModifierState('Alt') also
return true. This avoids the duplication.

2. When initializing "ctrlKey" or "metaKey" I define that the internal states
for getModifierStates "Control" and "Meta" are set (as described above), but
also that the virtual "Accel" modifier is also set. So initializing "ctrlKey"
to true will cause calls to getModifierState("Control") and
getModifierState("Accel") to also return true.

3. Given #2 above, I'm going to assume that if either "ctrlKey" OR "metaKey" is
true, then "Accel" is also true, rather than using ("ctrlKey" AND "metaKey")
logic.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 12 June 2014 17:45:47 UTC