Andy Goryachev
Andy Goryachev
Yeah, that's why I tried to hide this from the public. I see the whole create-multiple-events idea as a _bad design_ (tm), so the proposed change is a hack^H^H^H workaround...
> * Implement [JDK-8303209](https://bugs.openjdk.org/browse/JDK-8303209) > * Specify that `dispatchEvent` must only return `null` if the event was consumed. > * Explicitly document that `Event.isConsumed()` can only be used inside of...
Actually, no CSR is required if I revert the `final` keyword changes.
/csr unneeded
Removed 'final' keyword from existing public APIs. The changes are limited to TextFieldBehavior and SpinnerSkin.
> An EventDispatcher that creates a new event without linking it to the original will break this PR. But that's a consequence you're creating. You can't say the developer is...
> If a perfectly legal, properly written dispatcher in the chain creates a new event As I mentioned earlier, this is the problem of the dispatcher. Anyone can fire an...
you are right, csr **is** needed. /csr
> There are rules for how a dispatcher works. A dispatcher that follows those rules can still break this PR. Here are the rules (in EventDispatcher interface): ``` /** *...