greg-dove commented on issue #1170: URL: https://github.com/apache/royale-asjs/issues/1170#issuecomment-997452345
At the moment there are conversions from browser events into Royale events based on constructor name for things like MouseEvent, KeyboardEvent. These probably only work for browser/user generated events I think. And for outbound events (dispatched manually from Royale code), if they have an event-type name that is also 'native' (like 'change' or 'mouseup' for example) they are created as native browser events (always 'Event', never anything specific like 'MouseEvent' in this case I think) and sent through the dom. I don't know whether this approach is needed in all cases to create expected behavior or state change in native browser components for example, but that is how it is done currently, and I assume that is the reason behind it. And I haven't changed this behavior. I just added the Royale event to tag along with the browser event so that it can be retrieved for its royale listeners in the listener override. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
