-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cover: unable to set Left value in the focal point picker #28487
Comments
Addition: I noticed that it's possible to adjust the |
There was a recent fix around this: #28350 |
I cherry-picked that to the 9.8 branch tho, so it should be included in the release this was tested with 🤔 Could be related to one of the other recent Cover block fixes/adjustments? cc /@jasmussen |
I believe this was caused in #28096 because updateBounds was added to This results in a division by 0 which errors out and sets the left of the focal point picker to be Pinging @ItsJonQ since he might see a better way to handle this? |
That does appear to have been a separate issue. It's likely Brent has identified the cause for this in the above comment. I'd already made #28406 to address this (it didn't have any issues I could find at the time). The code differs trivially but does the same thing as #28499 and I threw in a doc fix 🤷♂️ |
Since the Focal Point Picker has been a bit fragile lately, it'd be great if we could add some e2e test coverage to the Cover Block e2e test (possibly alongside a fix, such as #28499). Anyone on this issue who'd like to give this a shot? 🙏 |
The performance of dragging also seems a bit clunky to me. |
Description
Since 9.8.0 for the Cover block I'm unable to set the
Left
value in the focal point picker.Step-by-step reproduction instructions
Left
value in the focal point pickerExpected behaviour
It'd set the
Left
value accordingly.Actual behaviour
It doesn't set the
Left
value at all.Screenshots or screen recording (optional)
focal-point-picker.mp4
WordPress information
All other plugins except for Gutenberg have been deactivated.
Device information
/cc @sirreal
The text was updated successfully, but these errors were encountered: