On Wed, 22 Apr 2020 15:52:11 GMT, Jeanette Winzenburg <faste...@openjdk.org> wrote:
> Compared to current state, there's a subtle side-effect (the event bubbles up > if the mapping if removed). We can > achieve the same behavior (with the same side-effect) by making the mapping > consume depending on whether it is handled > (to select all) or not. Changing the behavior inside `selectAll` is also a good option (and much cleaner as well) > So whatever approach we choose (mappings being removed/added or their > handlers not/consuming doesn't matter), we would > have to do it for several keys. Plus we have the side-effect mentioned above. > The mass of change for all listviews has > a certain risk of breaking existing code. Think f.i. global accelerators that > might (or not) get triggered depending on > selection mode. It's sad that we can't easily override (InputMapping created in) `ListViewBehavior` :( ------------- PR: https://git.openjdk.java.net/jfx/pull/172
