Opened 2 weeks ago
Closed 4 days ago
#62535 closed defect (bug) (reported-upstream)
"Save" button in the posts editor not reliably usable since WordPress 6.7
Reported by: | joergwiesner | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | 6.7 |
Component: | Editor | Keywords: | needs-patch reporter-feedback |
Focuses: | ui, accessibility | Cc: |
Description
COmpared to WordPress 6.6 the Save button has changed look and feel but also lost accessibility.
In 6.7 and 6.7.1 there is only a very small area of the button upon which the mouse pointer changes to the way it shows when over a clickable element, so often you miss carrying out the save of your changes, bacause although you get the warning question "Do you want to leave the page/post?" you cannot really carry out the save.
Please reestablish that whole Save Button area is clickable.
Attachments (2)
Change History (7)
#2
@
13 days ago
- Keywords reporter-feedback added
Hi @joergwiesner and welcome to WordPress Trac!
I am also unable to reproduce this issue. The cursor changes for me when I hover over save draft, publish, and save.
I don't speak the language that is used in the interface, but I believe the screenshot is of the "save draft". In my test, the whole button changes background color, which I don't see in your screenshot.
It is almost as if something is above the button, preventing you from hovering over the correct element.
I am using Chrome Version 131.0.6778.86 (Official Build) (64-bit) on Windows 11.
Perhaps it is an issue with a specific browser?
It would be helpful if you could:
- Test with all plugins disabled
- Test with a default theme active
- Share more detailed information about the environment
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
6 days ago
#4
@
6 days ago
This might be related to GB67069 (as #62537 is).
If not, it should have its own issue in the Gutenberg repository.
https://github.com/WordPress/gutenberg/issues/new/choose
Reproduction Report
Description
This report validates whether the issue can be reproduced.
Environment
Actual Results
Additional Notes
Thank you for raising this ticket and bringing the issue to our attention.
I tested the bug in both WordPress versions 6.6.1 and 6.7.1 but was unable to reproduce it. Could you please provide detailed steps to reproduce the issue or share a video as a reference? This will help us investigate further and address the problem effectively.
Supplemental Artifacts:
v6.6.1 video: https://utfs.io/f/PL8E4NiPUWyO4dXlsM1UDlJKwpCPLiEmr1dOSWk93yz07n2Z
v6.7.1 video: https://utfs.io/f/PL8E4NiPUWyO7vsFzj9AWOSNT8iuxYqzcvCVIEKbQmF3njPo