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
I am experiencing an issue with cursor alignment in Chrome when using the Ace Editor, particularly when typing Asian characters. The cursor often misaligns with the text, which disrupts the typing experience. This problem is more evident with Asian characters that have glyphs extending above and below the baseline, making accurate cursor placement difficult.
To resolve this, I propose adding a feature that allows users to switch between the Ace Editor and a standard textarea. This flexibility would ensure better cursor alignment, especially when dealing with languages that include complex characters.
This issue has been acknowledged in the Ace Editor's GitHub repository (ajaxorg/ace#460), where other users have reported similar problems with cursor alignment in Chrome. Implementing a switchable editor feature would be a practical solution to this ongoing problem.
The text was updated successfully, but these errors were encountered:
I am experiencing an issue with cursor alignment in Chrome when using the Ace Editor, particularly when typing Asian characters. The cursor often misaligns with the text, which disrupts the typing experience. This problem is more evident with Asian characters that have glyphs extending above and below the baseline, making accurate cursor placement difficult.
To resolve this, I propose adding a feature that allows users to switch between the Ace Editor and a standard textarea. This flexibility would ensure better cursor alignment, especially when dealing with languages that include complex characters.
This issue has been acknowledged in the Ace Editor's GitHub repository (ajaxorg/ace#460), where other users have reported similar problems with cursor alignment in Chrome. Implementing a switchable editor feature would be a practical solution to this ongoing problem.
The text was updated successfully, but these errors were encountered: