-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Sidebar broken in playground when preview switches to compact layout #907
Comments
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Still an issue. |
@rijenkii is the issue still open? |
The issue is still reproducible on https://asyncapi.github.io/asyncapi-react/: |
🎉 This issue has been resolved in version 2.4.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
When opening the sidebar through the hamburger button on bottom right of the screen, it is drawn on the right border of the screen, or not drawn at all if you decrease the space dedicated to the preview.
Reproduced on Firefox 121 and Chromium 120.0.6099.216, Fedora 39.
Steps to reproduce
Paste the following into the playground:
Schema
Configuration
Then click on the hamburger button.
Expected result
Actual result
Troubleshooting
I have achieved the result in the "expected result" by removing
.w-full
from the parent of.sidebar--content
and hardcoding correct width on that element.The text was updated successfully, but these errors were encountered: