I’m not sure if this is something that should be fixed on Adobe’s end. If they
don’t want to fix it, we can change EditManager to accept both charCodes to
deal with the difference in Chrome.
Let us know what you hear back from Adobe and create a JIRA if necessary.
> On Aug 10, 2017, at 5:54 PM, Harbs <harbs.li...@gmail.com> wrote:
> The charCodes are not the same.
> I just tested in Firefox and it’s 122 with caps lock on.
> The Chrome Flash plugin is different and it’s probably dispatching different
>> On Aug 10, 2017, at 5:35 PM, Felipe Melo <fel...@snews.tv> wrote:
>> I have not tested the EditManager approach, but dispatching a new event with
>> the lower case char code solved the problem. I'm not happy with using this
>> kind of workaround but sometimes it is necessary :)
>> I just didn't get it why this problem only happens in Chrome, because the
>> char codes in all browsers are the same. At first, I thought that this was a
>> Flash Player problem, but the Adobe staff don't think so.
>> Anyway, thank you all for helping me.
>> - Felipe
>> View this message in context:
>> Sent from the Apache Flex Users mailing list archive at Nabble.com.