On Tue, 22 Aug 2023 20:46:21 GMT, Andy Goryachev <ango...@openjdk.org> wrote:
> The fix uses character BreakIterator instead of the logic that relies on > caretBounds/hitTest/rangeShape in TextInputControl.nextCharacterVisually(). > > I believe this is a more reliable method of navigation, as it behaves in sync > with the jdk break iterator, thought it might work differently around > grapheme clusters, considering a recent change JDK-8291660 > > This change also introduces TextInputControlHelper class (impl. detail) which > gives access to character- and word- break iterators cached by > TextInputControl (*some say* these iterators and associated editing logic > should be a part of Content implementation, but that's a discussion for > another day). @prrace can you please take a look? ------------- PR Comment: https://git.openjdk.org/jfx/pull/1220#issuecomment-1747794422