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

Behaviour for TileSelect when it becomes disabled #4292

Closed
1 task done
edleeks87 opened this issue Aug 6, 2021 · 3 comments
Closed
1 task done

Behaviour for TileSelect when it becomes disabled #4292

edleeks87 opened this issue Aug 6, 2021 · 3 comments

Comments

@edleeks87
Copy link
Contributor

Current behaviour

We had an issue raised previously (#4227) where the focus outline was remaining on the a disabled TileSelect. A fix was implemented where the TileSelect loses focus when it is disabled. https://codesandbox.io/s/optimistic-mendeleev-f4i19?file=/src/index.js

Expected behaviour

Some implementation teams have requested that once the disabled prop is removed the TileSelect, be focused again/ not lose focus. The current behaviour seems to match how html inputs behave as default (https://codesandbox.io/s/peaceful-banach-y1e0w?file=/src/index.js), so I think it would be worth having a UX investigate so we can ensure we implement the correct behaviour.

CodeSandbox or Storybook URL

https://codesandbox.io/s/optimistic-mendeleev-f4i19?file=/src/index.js

Suggested Solution

No response

Carbon Version

81.04

What browsers are you seeing the problem on?

Firefox, Chrome, Safari

What Operating System are you seeing the problem on?

MacOS

Anything else we should know?

No response

Confidentiality

  • I confirm there is no confidential or commercially sensitive information included.
@edleeks87
Copy link
Contributor Author

@harpalsingh @tempertemper would you guys be able to look at this when you have a chance please?

@mmaciorowski-sage
Copy link

Hi @harpalsingh do we have some more information about designs?

@edleeks87
Copy link
Contributor Author

Closed as current behaviour seems to match how html inputs should behave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants