Opened 3 years ago
Last modified 3 years ago
#55417 new defect (bug)
Text Highlighting Broken
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 5.9.2 |
| Component: | Editor | Keywords: | needs-testing-info reporter-feedback |
| Focuses: | ui | Cc: |
Description
Trying to add a custom HEX, RGB, or HSL colors using the UI is just broken. Trying to input values or paste in values doesn't work. I have tried disabling all plugins and have tested it on multiple wordpress.org sites. Editing the value in the code editor still works, but it's just less convenient. Hopefully, this can get fixed next update, thanks!
Change History (4)
This ticket was mentioned in Slack in #accessibility by ryokuhi. View the logs.
3 years ago
#4
@
3 years ago
I think Its Style(Beta) features a color picker Issue. maybe it's already reported before and I have seen it somewhere.
I am writing the steps to reproduce the issue so that someone can identify if it's a duplicate.
- Activate Twenty Twenty Two theme
- Go to Customize Page
- Toggle styles panel from the top bar.
- Choose colors component
- Create a new custom color.
- Where the color picker is open, toggle show details input from the icon button. (Make sure HEX is selected in the dropdown)
- Copy HEX
#f5f5f5
You'll see #f5f5f5 is changed to #f5f5f that is not what we expect there.
for RGB and HSL I think single Input is missing so you can't just paste colors that you already have saved or you're copying from somewhere else. currently, you'll have to add each individual value in 3 different inputs.
Quick note: Original reporter is using a color picker in a different component, but had the same problem as I described above.
Hello @notgeo, and welcome on WordPress Trac!
Thanks for spending part of your time to report this issue, which we reviewed today during the accessibility team's bug-scrub.
Unfortunately, we aren't able to completely understand the problem you are facing. Can you please provide a step-by-step list of instructions that we can follow to reproduce the bug?
From the little we were able to understand, anyway, we think that this isn't an accessibility issue, that is, an issue that mainly affects people with disabilities.
As such, I'm removing the accessibility focus, but please add more detailled instructions to reproduce and, in case you think this is really an accessiblity issue, feel free to add the focus back.