Closed JohnRDOrazio closed 3 years ago
This seems to be a non issue actually. Something might have gone haywire in my local repo after the main branch was renamed to trunk
. I have completely removed my local copy of my fork, renamed the main branch of my fork to trunk
, recloned my fork, and resynched to upstream Gutenberg repo. Now in my local wp-env
with WP 5.8 and Gutenberg 10.1.0, this issue is non existent. So I'm going to go ahead and close this.
I haven't yet encountered this problem in the current WordPress releases. However when testing the latest build of the Gutenberg plugin (which will eventually be incorporated into the WordPress core), I noticed the
label
for theSelectControl
component was positioned on the left side of theSelectControl
, effectively giving the component even less space than it already had. I see they added a new optionlabelPosition
, which theoretically defaults totop
so should not have been an issue. However it was an issue, and even when trying to explicitly setlabelPosition
totop
, it still rendered on the side. Perhaps the implementation is still being written, in any case I opened an issue on the Gutenberg repo to address this: https://github.com/WordPress/gutenberg/issues/29447Hopefully it will be looked into and fixed. With a few tests in the Chrome developer tools I was able to fix this by setting the
flex-direction
tocolumn
instead ofrow
. If it doesn't get fixed before Gutenberg is again incorporated into WordPress core, we will have to address the issue by forcing the styles in the BibleGet plugin.