-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Steps: Cannot style active step in unstyled mode #6870
Comments
@melloware The code for Functionally, it should be exactly the same as how it is handled in Specifically, the following lines should be adapted for use in the |
@gcko i agree. Do you want to take this one? |
@melloware sure I can take a look at implementing the functionality |
…ed on parent and context - Pull code from TabView.js and ensure it works correctly under steps - Put in some initial styling for `step` and `label` - TODO add typing for parent and context
Do not implement child props at the moment
* feat: #6870 Ensure steps can be programmatically styled based on parent and context - Pull code from TabView.js and ensure it works correctly under steps - Put in some initial styling for `step` and `label` - TODO add typing for parent and context * feat: #6870 Add typing to steps.d.ts Do not implement child props at the moment
Describe the bug
Hi,
I am using Steps component in unstyled mode and I am trying to define styles. I managed to style the component, but not to style the active step (like putting a different background color).
Here is the code for the theme :
and the basic component usage :
It seems that in steps theme we have access to
props
andstate
but I cannot manage to get a conditional expression to check if step is active or not...In the demo, the active style exists but I don't know how to create it.
What is the solution 🙏 ?
Thank you in advance,
Reproducer
No response
PrimeReact version
10.7.0
React version
18.x
Language
TypeScript
Build / Runtime
Vite
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: