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.

Sign up for GitHub

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

Jump to bottom

Provide component trace #4

Open
raunofreiberg opened this issue Apr 30, 2020 · 2 comments
Open

Provide component trace #4

raunofreiberg opened this issue Apr 30, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@raunofreiberg
Copy link
Owner

I haven't thought this through or done any research as to if it is even possible, but...

Would be really cool if instead of displaying the target node that axe-core gives us, we could show the component in which the node is present.

This might be possible by using the node. React DevTools does something similar. If you select an element on the page to inspect and then jump to the "Components" tab, it will highlight the component in which the node exists.

Might be worth looking into.
@raunofreiberg raunofreiberg added the enhancement New feature or request label Apr 30, 2020
@chaance
Copy link
Collaborator

chaance commented Apr 30, 2020

I think it could be useful to do both. Or better yet, perhaps, what if the component name linked directly to open up a tab in React Dev Tools if the user has it installed in their browser? Worth exploring for sure!

@raunofreiberg raunofreiberg mentioned this issue Apr 30, 2020
Merged
@raunofreiberg
Copy link
Owner Author

Or better yet, perhaps, what if the component name linked directly to open up a tab in React Dev Tools if the user has it installed in their browser?

I love this! Let's do this as a follow up for #5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chaance @raunofreiberg