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

🐛 bug : navigation tab is not working properly #1008

Open
aialok opened this issue May 30, 2024 · 3 comments · May be fixed by #1024
Open

🐛 bug : navigation tab is not working properly #1008

aialok opened this issue May 30, 2024 · 3 comments · May be fixed by #1024

Comments

@aialok
Copy link

aialok commented May 30, 2024

Description

  • Navigation tab between schema and configuration is not working as expected.

Expected Result

  • It should navigate properly between the schema tab and configuration tab.
Screencast.from.2024-05-30.17-23-42.webm

Actual Result

Screencast.from.2024-05-30.17-28-34.webm

Steps to Reproduce

  1. Go to the AsyncAPI website homepage.
  2. Click on the configuration tab.
  3. Click on the schema tab.
  4. Try to navigate back to the configuration tab.

Troubleshooting

  • I found there is issue in tabIndex. Basically in one of if statement we are checking tabIndex but tabIndex is value can equal to zero and schema tab tabIndex is zero so when navigating back to schema tab from configuration tab. If statement is not working and hence navigation is not working.
Copy link

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@aialok
Copy link
Author

aialok commented May 30, 2024

I would love to work on this issue : )

@derberg
Copy link
Member

derberg commented Jun 20, 2024

@aialok please go ahead and open a PR

@NEMYSESx NEMYSESx linked a pull request Jun 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants