We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Recently the ability has been added to hero blocks to select existing images. (Finally! Yay!)
But for existing images the dimension limits are completely ignored.
The cards are 800px wide, nowhere near to the required 1200px (claimed by the field help text). But they're accepted and inserted without nagging.
Nagging according to min width setting,
It seems like when improving the settings, somewhere on the road the validation was dropped (or never added). Validation for uploads work as expected.
I'm aware that selecting existing images from library is a bit flaky, but if the text claims that there's a min setting, I'd expect some validation.
It's not urgent, just one of those WTF, that should be fixed...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description of the bug
Recently the ability has been added to hero blocks to select existing images. (Finally! Yay!)
But for existing images the dimension limits are completely ignored.
Steps To Reproduce
Actual behavior
The cards are 800px wide, nowhere near to the required 1200px (claimed by the field help text). But they're accepted and inserted without nagging.
Expected behavior
Nagging according to min width setting,
Additional information
It seems like when improving the settings, somewhere on the road the validation was dropped (or never added).
Validation for uploads work as expected.
I'm aware that selecting existing images from library is a bit flaky, but if the text claims that there's a min setting, I'd expect some validation.
It's not urgent, just one of those WTF, that should be fixed...
The text was updated successfully, but these errors were encountered: