Skip to content
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

Move visually hidden space inside element #408

Merged
merged 1 commit into from
Mar 10, 2023

Conversation

peteryates
Copy link
Member

The final decision on how to properly handle the space between the visible and hidden text hasn't been made yet but the general consensus upstream is that it's better inside the visually hidden span than before it.

This might be revisited again when a decision has been made and the solution presented in #403 can be used instead.

@netlify
Copy link

netlify bot commented Mar 10, 2023

Deploy Preview for govuk-components ready!

Name Link
🔨 Latest commit c093a87
🔍 Latest deploy log https://app.netlify.com/sites/govuk-components/deploys/640b06d413550a00089402f8
😎 Deploy Preview https://deploy-preview-408--govuk-components.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Copy link
Collaborator

@frankieroberto frankieroberto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I think we can merge this straight away, as it’s what the nunjucks component already does?

Do we consider this a breaking change? I guess it might break some downstream tests, depending on how they were written?

The final decision on how to properly handle the space between the
visible and hidden text hasn't been made yet but the general consensus
upstream is that it's better inside the visually hidden span than before
it.

This might be revisited again when a decision has been made and the
solution presented in #403 can be used instead.
@peteryates peteryates force-pushed the move-space-before-visually-hidden-text-inside-span branch from 1e6ebca to c093a87 Compare March 10, 2023 10:30
@peteryates
Copy link
Member Author

Yeah it's definitely a breaking change but the next release will be a big one anyway so the timing is good.

@peteryates
Copy link
Member Author

I added a note to the release notes issue #390

@peteryates peteryates mentioned this pull request Mar 10, 2023
4 tasks
@peteryates peteryates added this pull request to the merge queue Mar 10, 2023
Merged via the queue into main with commit f0410b2 Mar 10, 2023
@peteryates peteryates deleted the move-space-before-visually-hidden-text-inside-span branch March 10, 2023 10:41
peteryates added a commit to DFE-Digital/early-careers-framework that referenced this pull request Aug 16, 2023
peteryates added a commit to DFE-Digital/early-careers-framework that referenced this pull request Aug 16, 2023
peteryates added a commit to DFE-Digital/early-careers-framework that referenced this pull request Aug 16, 2023
ltello pushed a commit to DFE-Digital/early-careers-framework that referenced this pull request Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants