- From: <bugzilla@jessica.w3.org>
- Date: 2015年2月11日 01:59:48 +0000
- To: www-dom@w3.org
- Message-ID: <bug-26019-4009-f307Md6HAm@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26019 Travis Leithead [MSFT] <travil@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Travis Leithead [MSFT] <travil@microsoft.com> --- (In reply to Travis Leithead [MSFT] from comment #8) > (In reply to Anne from comment #5) > > Travis, note that if your initialization process is not covered by > > http://dom.spec.whatwg.org/#constructing-events we need to figure out how to > > make that work. You might have to define the entire constructor yourself. > > Mmm. DOM doesn't seem to have the hooks I need. I need some internal state > that can represent the possible values used by the getModifierState > function... I should be able to whip that up. Committed a rough extension to Anne's algorithm in the DOM spec. https://dvcs.w3.org/hg/dom3events/rev/ad15280ceb0c -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 11 February 2015 01:59:50 UTC