On 11/20/13 5:38 AM, "MVBaker" <[email protected]> wrote:
>My idea was that using the getDefinitionByName would allow the function to >work as intended with whatever extension of MouseEvent was used rather >than >bypassing it if it was an extended class. Should we only apply this >transformation of !cancellable to cancellable if it's the super class? I think the goal is simply to make raw MouseEvents cancelable. IMO, no subclasses of MouseEvent should need to be transformed. When any subclass gets instantiated you can choose cancelable then. You don't get to choose for player-generated MouseEvents. >While we're looking at this I have a question that I didn't think of >yesterday. What happens with the properties of the extended class or if >the >MouseEvent class gets a new property in a future version? Another reason not to handle MouseEvent subclasses in this method. If MouseEvent does get extended we'd have to change the code. -Alex
