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

[docs] Toggle left-to-right/right-to-left reverses the tag start and tag end on API's component name. #21385

Closed
gulzarsuhail opened this issue Jun 10, 2020 · 2 comments · Fixed by #21386
Labels
accessibility a11y docs Improvements or additions to the documentation

Comments

@gulzarsuhail
Copy link

On clicking the Toggle left-to-right/right-to-left button, the components listed in the API section on each page get their tags reversed.

For example, <Button/> on clicking the toggle becomes </ Button> . On re toggling, the
tags are back in their original position when viewed in Firefox or Edge but on Chrome, component's API becomes >Button</.

This issue is prominent on all docs pages with API's containing a component name in tags.

@gulzarsuhail gulzarsuhail added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Jun 10, 2020
@eps1lon
Copy link
Member

eps1lon commented Jun 10, 2020

What's even weirder that switching twice results in >Alert</ which is even worse: https://material-ui.com/components/alert/#api

@eps1lon eps1lon added accessibility a11y docs Improvements or additions to the documentation and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Jun 10, 2020
@gulzarsuhail
Copy link
Author

Yes, though the double switch issue is only applicable in Chrome. Firefox and Edge seem to revert the tags to their original positions (as mentioned above).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility a11y docs Improvements or additions to the documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants