Repository navigation
fix(docs): prevent mobile horizontal overflow - #398
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe CSS changes adjust the standards grid sizing and mobile layouts for footer links and the closed navbar. ChangesResponsive Layout Adjustments
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The changes address the reported mobile width issues with scoped layout rules, and the reported browser checks confirm the target widths. No merge-blocking risk is apparent; proceed with normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🧪 Generate unit tests (beta)
🛠️ Fix failing CI checks 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the narrow grid, Comment |
|
❌ Surge preview build failed — no preview was deployed. Check the workflow logs for details. Once the build passes, the preview will be at: https://opentdf-docs-pr-398.surge.sh Common cause: If the build failed on vendored YAML validation, run the following locally and commit the result: |
Summary
Bug report and visual evidence
Mobile screen recording in Slack
On a 390 px viewport, the page width grew to 714 px after the navbar hid. With the CSS fix applied, it stays at 390 px. The mobile menu still opens normally.
Validation
git diff --checkpassed.npm run buildpassed with Node 22 after the import fix. The generated Configuration and OIDC pages link to each other correctly.Remote content maintenance
The import currently follows
opentdf/platformmain, so upstream edits can change this site's build without a docs commit. The link rewrite handles new relative Markdown links by sending unimported pages to their upstream source; external targets are not checked by Docusaurus. If upstream changes keep disrupting CI, pin this import to a reviewed commit or release and update that ref through a scheduled PR with a full site build.Summary by CodeRabbit