WordPress.org

Make WordPress Core

Opened 14 months ago

Closed 14 months ago

Last modified 14 months ago

#47180 closed defect (bug) (fixed)

Gutenberg typing issues in RTL since 5.2

Reported by: salar6990 Owned by: iseulde
Milestone: 5.2.1 Priority: high
Severity: critical Version: 5.2
Component: Editor Keywords: has-screenshots
Focuses: rtl, administration Cc:

Description

When Site has an RTL Locale (like Persian/فارسی in my case) Arrow right, arrow left and backspace keys show invalid behavior in Gutenberg editor:
arrow right and arror left move the text cursor in the opposite direction
and when the text cursor is at the end of sentence, backspace key would move the cursor to previous block or loose the focus from the current block and even could move the text to that block!

Attachments (1)

problem.mp4 (86.5 KB) - added by man4toman 14 months ago.

Download all attachments as: .zip

Change History (14)

#1 @iseulde
14 months ago

  • Owner set to iseulde
  • Status changed from new to assigned

Looking into it.

#3 @man4toman
14 months ago

Also, in text block, if we move arrow to right at the start line of text, arrow goes left and right and remain in a loop!

Please check the video.

@man4toman
14 months ago

#4 @man4toman
14 months ago

  • Component changed from General to Editor
  • Focuses administration added
  • Keywords needs-patch added

#6 @iseulde
14 months ago

  • Focuses rtl added

#7 @SergeyBiryukov
14 months ago

  • Milestone changed from Awaiting Review to 5.2.1

#8 @iseulde
14 months ago

  • Priority changed from normal to high

#9 @iseulde
14 months ago

  • Keywords has-patch added; needs-patch removed

#10 @iseulde
14 months ago

(Patch can be found on Github, but still refining it.)

This ticket was mentioned in Slack in #core by ella. View the logs.


14 months ago

#12 @desrosj
14 months ago

  • Keywords has-screenshots added; has-patch removed
  • Resolution set to fixed
  • Status changed from assigned to closed

A fix for this was included in [45319] and backported in [45320] (see #47284).

Thank you, @man4toman and @salar6990!

#13 @man4toman
14 months ago

Well done, thanks.

Note: See TracTickets for help on using tickets.