On Tue, 25 Feb 2020 13:55:50 GMT, Nir Lisker <nlis...@openjdk.org> wrote:
> > > I think that a starting point would be to decide on a spec for the listener > notification order: is it specified by their registration order, or that is > it unspecified, in which case we can take advantage of this for better > performance. Leaving is unspecified and restricting ourselves to having it > ordered is losing on both sides. technically true - but the implementation was linear with a fixed sequence since-the-beginning-of-java-desktop-time (and sometimes, for good ol' beans properties, even exposed as api to access the array of listeners). So technically, we could go the path of explicitely spec'ing that the order is unspecified. Pretty sure that doing so and implementing it will break tons of application code that's subtly relying on fifo notification (f.i. register before or after skin has its own is a simple wide-spread trick) .. which all did it wrong and might deserve it ;-) But then if even internal code does it .. ------------- PR: https://git.openjdk.java.net/jfx/pull/108
