We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug
RTL
Scenario 1: 3. Place caret at the end of line (after world) 4. Press right arrow
world
Caret moved left (that's default in RTL)
Caret is stuck in the same place
Scenario 2: 3. Place caret in the middle of line (e.g. between words) 4. Try to navigate to the ! using right arrow
!
Navigation is intuitive and caret moved character by character.
When caret is between letters H and e and right arrow is pressed, caret is moved to the end (beginning) of the line.
H
e
It looks similar as #2104, which however turned out to be an upstream issue.
4.14.0
4.10.0
BiDi
The text was updated successfully, but these errors were encountered:
It seems to be Chrome's bug as it's reproducible also without CKEditor 4 instance: https://jsfiddle.net/Comandeer/mn8h76tw/
Sorry, something went wrong.
Confirmed - Chrome and Edge are broken. I'm reporting an issue in Chromium tracker.
Closing issue as an upstream - https://bugs.chromium.org/p/chromium/issues/detail?id=1055757.
No branches or pull requests
Type of report
Bug
Provide detailed reproduction steps (if any)
RTL
text direction for the first paragraphScenario 1:
3. Place caret at the end of line (after
world
)4. Press right arrow
Expected result
Caret moved left (that's default in RTL)
Actual result
Caret is stuck in the same place
Scenario 2:
3. Place caret in the middle of line (e.g. between words)
4. Try to navigate to the
!
using right arrowExpected result
Navigation is intuitive and caret moved character by character.
Actual result
When caret is between letters
H
ande
and right arrow is pressed, caret is moved to the end (beginning) of the line.Other details
It looks similar as #2104, which however turned out to be an upstream issue.
4.14.0
,4.10.0
BiDi
The text was updated successfully, but these errors were encountered: