|
|
|
[
Permlink
| « Hide
]
P T Withington - 27/Mar/08 05:17 AM
I suspect this is because the OS or App is intercepting the key-combo (because it is defined as a shortcut in either the OS or App). Probably the kernel needs to tell the browser that it want's to receive these keycombos when an LZX app tries to listen to them. (Somehow Jira seems to take over all my OS shortcuts, which drives me nuts; but if this is what we want to do, I guess we should do the same thing. Personally, I think it is very rude for a web app to subvert my platform shortcuts for its own purposes!)
Btw, this is a regression on Windows. Not a 100% sure it's a regression on Macs.
Date: Thu, 27 Mar 2008 09:48:06 -0700 (PDT)
From: Matt Kolenda <mkolenda@laszlosystems.com> We treat regressions as P1 issues. This should be fixed by our release=20 candidate which is tomorrow end of day. I suppose we could wait until=20 Monday at the latest. Seems more serious. I ran into a similar problem trying to use ctl-enter (running IE 7.0, swf8). Upon investigation it looks like something funny happens to the modifier keyup events.
With the program below perform the sequence: shift-down, a-down, a-up, shift-up The shift-up is not reported until you toggle the shift key, e.g. shift-down, shift-up <canvas debug="true"> <handler name="oninit"> super.init(); this.ddel = new LzDelegate(this, 'keydown', LzKeys, 'onkeydown'); this.udel = new LzDelegate(this, 'keyup', LzKeys, 'onkeyup'); </handler> <method name="keyup" args="kc">Debug.write('u', kc);</method> <method name="keydown" args="kc">Debug.write('d', kc);</method> </canvas> Ooops, should not have had the super.init() in my sample code, still broken even without it.
This is a swf8 issue (at first I thought it was a dhtml issue). As far as I call tell, IE7 is stealing these keypresses and I don't know how to get them back. If you run the second testapp using control-g, it works fine. control-a is a keyboard shortcut in IE7.
This appears to be a bug in the flashplayer. See
http://bugs.adobe.com/jira/browse/FP-118 http://bugs.adobe.com/jira/browse/FP-106 These bugs list the OS as Vista but I have verified it happens in XP as well. One possible workaround is to write the app to use onkeyup and not onkeydown. Max suggested a workaround of having the DOM generate the events, but this involves changing the kernel. Lou - please document that this is a known issue (an Adobe bug) in the release notes. Please be sure to include a full description of the problem manifestation. Once added, please assign the JIRA bug back to me. The real fix will be deferred until Adobe fixes the problem.
|
||||||||||||||||||||||||||||||||||||||||||||||||