Opened 9 years ago
Closed 7 months ago
#33049 closed enhancement (fixed)
Media Library toolbar: spinner position on small screens
Reported by: | afercia | Owned by: | joedolson |
---|---|---|---|
Milestone: | 6.5 | Priority: | normal |
Severity: | normal | Version: | 4.2 |
Component: | Media | Keywords: | has-screenshots has-ui-feedback has-patch commit dev-reviewed fixed-major |
Focuses: | ui | Cc: |
Description
After 31996 the spinner position is now generally improved across the admin. There are still places where it can be further improved though, especially for small screens.
Please see the screenshot below, on the left how the spinner is currently being displayed. Since it's hidden with visibility: hidden
it does reserve space and thus there's a big space between form elements.
Considering also translations, the form fields length is unpredictable, they could be displayed in three rows or four rows or just tow, depending on the viewport width and basically there's no easy CSS solution if we still want to display the spinner "inline".
One possible solution could be the one on the right in the screenshot: under a certain viewport width, just give the spinner an absolute position in order to have it centered in a semi-transparent overlay. This would work regardless of the form fields length, number of lines, etc.
I'm not a designer :) but I'd like to bring this to the UI/design team attention.
Attachments (4)
Change History (28)
This ticket was mentioned in Slack in #design by afercia. View the logs.
9 years ago
#5
@
8 months ago
- Keywords has-patch added
The loader is now in center with white Background overlay under ‘’media-782'’.
So, Please check the attached diff file and Share your feedback on it.
Thanks!
This ticket was mentioned in Slack in #core by audrasjb. View the logs.
8 months ago
@
8 months ago
Update patch to properly show/hide the overlay; rename property to tertiary instead of third for consistency
This ticket was mentioned in PR #6097 on WordPress/wordpress-develop by @joedolson.
8 months ago
#8
Trac ticket: https://core.trac.wordpress.org/ticket/33049
@joedolson commented on PR #6097:
8 months ago
#11
in r57605
#12
@
7 months ago
Could folks help me confirm if https://core.trac.wordpress.org/changeset/57605 affects the ability of the media library to add new images in narrow viewport widths in the editor?
I think the new overlay is making the button unclickable. Furthermore, the button is not disabled via any attribute but by an overlay div (.media-bg-overlay
), therefore I'd argue it probably constitutes an accessibility problem as well.
See .media-bg-overlay
here:
Reported here https://github.com/WordPress/gutenberg/issues/60152 in case the fix lies with Guteberg, but I think it should be fixed in Core?
Thanks!
#13
@
7 months ago
Could folks help me confirm if https://core.trac.wordpress.org/changeset/57605 affects the ability of the media library to add new images in narrow viewport widths in the editor?
Maybe it's a typo in the CSS value? I don't think that display:hidden
is correct CSS.
This ticket was mentioned in PR #6313 on WordPress/wordpress-develop by @ramonopoly.
7 months ago
#14
display: hidden
is invalid CSS
It's causing the following bug:
https://github.com/WordPress/gutenberg/issues/60152
Trac ticket: https://core.trac.wordpress.org/ticket/33049
#15
@
7 months ago
- Resolution fixed deleted
- Status changed from closed to reopened
Maybe it's a typo in the CSS value? I don't think that display:hidden is correct CSS.
I just saw this too! Thanks @wildworks
I updated a Core patch to correct
@swissspidy commented on PR #6313:
7 months ago
#16
Ah, that's why I wasn't able to insert images on my phone! 💡
@swissspidy commented on PR #6313:
7 months ago
#18
Committed in https://core.trac.wordpress.org/changeset/57881
@ramonopoly commented on PR #6313:
7 months ago
#19
Thanks for taking care of that @swissspidy
This ticket was mentioned in Slack in #core-media by joedolson. View the logs.
7 months ago
#21
@
7 months ago
- Keywords dev-reviewed added
- Resolution fixed deleted
- Status changed from closed to reopened
Reopening for merge to 6.5 branch; reviewed and ready for merge.
I would +1 to giving a transparent overlay and being the left option. To me having a consistent play for the eye makes a lot of sense to users. I am also all for unifying any interaction or feedback like this.