-
Notifications
You must be signed in to change notification settings - Fork 15
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
replace unmaintained chip-input lib #61
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/stateful/vscode-marquee/GDLyom89JtEpCpbsZtPFHwiEd8uK [Deployment for 6ef1b43 canceled] |
MUI noob here: what's the best way to prevent the label-adornment overlap from happening? Any advice @christian-bromann ? |
b14c6ef
to
cb5982c
Compare
d9117b0
to
79e44cb
Compare
|
||
const tagToRemove = screen.getByRole("button", { name: tagToRemoveLabel }); | ||
|
||
userEvent.click(tagToRemove.querySelector("svg")!); |
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.
Unfortunately the MUI Chip (and MUI generally) has not the greatest a11y (as they admit themselves), which makes it also harder to test at times. So I have to directly address the svg tag.
Interestingly in their own tag, they swap out the default delete icon to test it.
79e44cb
to
f456ac3
Compare
ea4245a
to
db23a4b
Compare
db23a4b
to
14608ee
Compare
14608ee
to
e4f2f55
Compare
e4f2f55
to
ebaff76
Compare
ebaff76
to
a4ff293
Compare
a4ff293
to
6ef1b43
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.
Awesome 👍
See #45 (comment)