AdvancedCustomFields / AdvancedCustomFields/acf
Text highlighting doesnt work in WYSIWYG field like a default post TinyMCE editor does
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Hi Support
When using the default Tinymce editor attached to a post, it is possible to select text in visual mode, click the code view, and have the text still selected. When trying the same in a WYSIWYG field, the text does not remain selected.
The same issue is demonstrated when using Gutenberg as the main editor too.
WordPress: 5.8.2
ACF: 5.11.4
Theme: Twenty Twenty-One
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the selection behavior in an ACF WYSIWYG field, comparing it with the default WordPress post editor using TinyMCE and with Gutenberg. Start from the WYSIWYG field and editor integration entry points; done means selected text remains selected after switching from visual mode to code view in the affected editors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- content
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100