-
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
Improve display of shortcode block in columns #11079
Comments
Can reproduce this as well on Gutenberg 4.1.1 with WordPress 4.9.8 on Google Chrome Version 70.0.3538.67 (Official Build) (64-bit). macOS 10.14 - Mac OS Mojave. 3 shortcode blocks inside the columns blockImage indicating how the shortcode block content region is small when the shortcode label is on the leftOn adding more textAnother image indicating how the shortcode block content region is small when the shortcode label is on the leftSuggested formatI am going to take a stab at submitting a PR for this to bring it in the format shown below. Image indicating the shortcode label at the top of the content, as opposed to being on the left |
A temporary fix when you're editing a shortcode is to edit the CSS to and/or do as Bill suggested and disable the padding as well. For the front-end view see https://wordpress-seo.wp-a2z.org/ |
With Gutenberg 5.5.0 I now get This is due to a new problem. #15032 |
I'm on Wordpress 5.2, and I still have the OP's behaviour with shortcodes (7 months after it was posted!). Adding |
I agree with @talldan here. The alignment issues have been resolved, but it would be good to set the textarea width to 100%. Currently Width at 100% |
Describe the bug
The shortcode block label is floated to the left of the textarea. While this works well in larger contexts, inside the columns block this shrinks the texarea down to one character per line:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The textarea should be larger and more usable. Float the label above the textarea and make them both full width.
Screenshots
The text was updated successfully, but these errors were encountered: