-
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
Pre-publish panel panels lack spaces between titles and labels #7842
Comments
👍 I've been noticing this too but never got around to create a ticket for it. |
Only concern I have about CSS padding is what happens if you select and copy/paste that text — presumably there's no space being copied? Also, what's the impact on screen readers if the space isn't in the markup? |
These are clickable titles that open up panels, so I'm not sure there'd be a way of copying and pasting the text. (This is me trying!) The screenreader issue is a valid concern, although I wasn't able to find solid documentation one way or another to indicate how a screenreader would handle a case like this. Would the colon and the span be enough to force a space in the way it's read? I could leave the whitespace in the title, but that doesn't seem to be best practise. From the i18n documentation:
I suspect this is because GlotPress may not display leading/trailing whitespace in an obvious way, which means the string would be likely to be translated without the trailing whitespace—which means we'd have the same issue with other languages. |
Issue Overview
There isn't any space between the titles and the labels of panels inside the pre-publish panel:
Steps to Reproduce (for bugs)
Looks as though the translation strings here are written with the intention of there being a single space here (
<PanelBody title={ [__( 'Visibility: ' )] }>
), but that trailing space is removed when the text string is run through the translation function. Text strings aren't supposed to use trailing whitespace, so a little bit of CSS padding is probably a better solution here.Sort of related (if pretty tangentially): #7426
The text was updated successfully, but these errors were encountered: