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

refactor(inputs): updating focus styles [WIP] #14

Closed
wants to merge 2 commits into from

Conversation

gavin-everett-genesys
Copy link
Collaborator

Open to opinions on this change before I do the rest of the inputs.

https://inindca.atlassian.net/browse/COMUI-2348

COMUI-2348

updating focus styles

COMUI-2348
@github-actions
Copy link

Demo will be published at https://apps.inindca.com/common-ui-docs/genesys-webcomponents/feature/COMUI-2348

update focus stylings

COMUI-2348
@@ -137,6 +137,7 @@ export class GuxFormFieldNumber {
</GuxFormFieldLabel>
<div class="gux-input-and-error-container">
<div
tabIndex={1}
Copy link
Collaborator

Choose a reason for hiding this comment

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

This seems like a bad idea to me. Why do you need to make this change?

https://whattrainisitnow.com/calendar/ looks like we have to wait until next October to use the :has selector :(

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

UX want to have the focus-ring around the component when a keyboard user is navigating to the component and not when the user has clicked the component via a mouse click. So my thought was if I use :focus-visible on the container div and then use :focus-within in the inner div to apply the active styling. So that if the user was to mouse click it will only show active styling.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

From what I read on the mozilla form it should be released in firefox 120 as its already in the 119.0a1 beta. So potentially this November 🙌
https://www.mozilla.org/en-US/firefox/119.0a1/releasenotes/

Copy link
Collaborator

Choose a reason for hiding this comment

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

AFAIK we support Firefox Extended Support Release which is currently v115 and won't change until v128.

@daragh-king-genesys
Copy link
Collaborator

@gavin-everett-genesys I think we can close this for now. UX is going to look at it again and maybe align with focus-visible.

@daragh-king-genesys daragh-king-genesys deleted the feature/COMUI-2348 branch November 10, 2023 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants