-
Notifications
You must be signed in to change notification settings - Fork 92
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
fix: adjust active element visibility in nclistitem #4158
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
23e3d5f
to
6ba9ff4
Compare
@marcoambrosini can you help me to get an active element as example into the docs? This would make testing this a bit easier :) |
Looks good in the screenshot, but as Marco said the dot needs to be adjusted, it can be changed to white :) |
Looks good, and yep as @nimishavijay said switching the dot to white on the active element is good, so it’s symmetric to the "message for you" counter bubble color. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, thank you!
contrast of "talk icon" should't be increased because it is only a decorative icon
Identify each graphic on the page that includes information required for understanding the content (i.e. excluding graphics which have visible text for the same information, or are decorative)
from https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html
@szaimen just add the |
4a7ad19
to
f1e5562
Compare
thanks for the pointer! Works great! :) |
f1e5562
to
654c048
Compare
Probably i haven't understood a problem, but why we could't add an |
I fear the problem is that this should probably be done automatically for embedded components? Also there is not active state for nccounterbubble for example afaik... |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
@JuliaKirschenheuter would you mind taking this over? I am unfortunatley techincally stuck on how to proceed here. |
I can take over :) |
Thanks a lot Marco! 💙🙏 |
I just reworked a bit. @skjnldsv @raimund-schluessler @susnux do you think this would cover all the use cases? Maybe we should also include a prop to force-primary style in the cases where the element is not a router link? |
The screenshot looks good to me :) Can you commit your changes? They arent yet afaics |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good design-wise! :)
This comment was marked as off-topic.
This comment was marked as off-topic.
an |
This comment was marked as resolved.
This comment was marked as resolved.
654c048
to
a962c4d
Compare
@szaimen yeah, the icon needs to invert then to the same as text color (white in the case of default blue primary color). |
That is because the element is not activated unless the route is matched. I'm adding a "forceactive" prop now |
a962c4d
to
669c3b3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Marco <marcoambrosini@icloud.com>
669c3b3
to
2412bbf
Compare
Should be fixed now @szaimen! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! :)
todo: