You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a chance that an extreme edge case might still have issues:
Suppose a keyboard rule that changes the last character before the newline preceding the caret. (Say, a\n + b => b\n.)
Now suppose that rule is triggered by a multitap key, thus cycling in and out during multitap rota alongside context rewind operations.
As the tap with the rule would trigger an edit (within the host app) past context-window boundaries, this would naturally trigger context-synchronization after the related tap should the textDocumentProxy perform a context-window jump as a result... and also for the tap after it, which would need to make counter-edits to revert such a rule's change, as such a tap would likely retrigger a textDocumentProxy update.
Upon request, I suppose I could create a highly-focused test keyboard for validating such a case. That said, it does seem pretty niche - I don't think we currently have a keyboard with such rules. (As a result, I haven't prioritized testing this scenario.) [...]
The text was updated successfully, but these errors were encountered:
From #10728:
The text was updated successfully, but these errors were encountered: