On Tue, 29 Oct 2024 19:33:20 GMT, Andy Goryachev <ango...@openjdk.org> wrote:
> It's one of the falsehoods programmers should be aware of. > > But regardless of how they interact with the UI, the focus indicator should > always indicate the focus owner, no? There might be levels of indication, > such as grayed focus border when the component does not have input focus, vs > blue focus border when it does, but there should never be a situation when > the component **has input focus and no indication**, right? No, you're clearly in the wrong here. Just go to a random native macOS or Windows 11 application and show me the focus indicators. You won't see them in almost all cases. You're trying to re-litigate common concensus across operating systems and [on the web](https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible), and in the process ignore all precedent and the thinking that lead to the state of the art. > Applying this logic to the issue at hand, we probably should drop the boolean > argument and say it "is expected to be called in response to a KeyEvent", > that is, do not give the user the choice they don't need (or want). > > What do you think? I don't see how your argument against `focusVisible` has anything to do with the question at hand. ------------- PR Comment: https://git.openjdk.org/jfx/pull/1604#issuecomment-2445216433