To reproduce:
Observed: The Arabic letters next to which the caret moves are disconnected.
Expected: Moving the caret must only move the caret. It must not change the appearance of the text.
This works well in Firefox, but broken in Chrome.
Version: unspecified
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Jdforrester-WMF | T53792 VisualEditor: Non-English Wikipedia issues (tracking) | |||
| Invalid | Jdforrester-WMF | T35077 VisualEditor multilingual input / i18n issues (tracking) | |||
| Open | None | T84936 Release VisualEditor-MediaWiki as "1.0" | |||
| Resolved | Amire80 | T68339 VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters |
I am not sure what fixed it, but it works for me now in Chrome 36.0.1985.143 on Fedora 20.
Can this be tested automatically to prevent regression?
Be sure to also test in a recent version of Safari (which runs on WebKit).
Chrome hasn't been based on WebKit for almost 2 years now. It's using Chromium/Blink instead.
Well, I reported it, and I only have Chrome on Linux, so I guess I meant "Chrome" or "Blink" and not "WebKit".
(In reply to Amir E. Aharoni from comment #3)
Well, I reported it, and I only have Chrome on Linux, so I guess I meant
"Chrome" or "Blink" and not "WebKit".
If it was present in Chrome at that point in time though, depending on whether it was a recent regression in Chrome, it likely still exists in WebKit/Safari (since Blink is a fork of WebKit).