Gutenberg Paragraphs: dir="LTR" results in unexpected or invalid content error #67354
Labels
Customer Report
Issues or PRs that were reported via Happiness. Previously known as "Happiness Request".
[Platform] Atomic
[Platform] Simple
[Pri] Normal
Schedule for the next available opportuinity.
[Status] Core Fix Needed
A fix within the Core WordPress or Gutenberg project is required to resolve this issue.
Triaged
To be used when issues have been triaged.
[Type] Bug
When a feature is broken and / or not performing as intended
Quick summary
Content creators who use RTL and LTR languages in their sites have been able to reverse text direction for a given paragraph block by editing its HTML and adding
dir="LTR"
ordir="RTL"
. This stopped working in a recent update: creating paragraphs with that HTML edit, or editing a post that already has those types of paragraphs, results inunexpected or invalid content error
messages that can't be recovered without stripping the text direction. Block recovery doesn't help; the setting gets removed.Steps to reproduce
dir.rtl.mov
What you expected to happen
Honestly I'd expect a text direction option in the paragraph block's settings, or just for blocks in general. But if we must hand-edit the HTML, we need to accept it as valid.
What actually happened
We get a block error with an offer to attempt recovery, which just removes the text direction.
Context
https://wordpress.com/forums/topic/left-to-right-english-text-in-right-to-left-hebrew-blogs-is-mis-directed/
Platform (Simple, Atomic, or both?)
Simple, Atomic, Self-hosted
Theme-specific issue?
n/a
Browser, operating system and other notes
n/a - this isn't a browser so much as an issue with what code we accept as valid.
Reproducibility
Consistent
Severity
Some (< 50%)
Available workarounds?
Yes, easy to implement
Workaround details
The workaround is to ignore the error and publish anyway, but it's kind of annoying to no longer be able to see the block text in the editor. Or, we can convert to an HTML block instead. But it would be better to fix the issue.
The text was updated successfully, but these errors were encountered: