Skip to content

docs: restore full-width search layout - #131

Merged
LimiNode merged 10 commits into
mainfrom
docs/sidebar-theme-toggle
Sep 11, 2026
Merged

docs: restore full-width search layout#131
LimiNode merged 10 commits into
mainfrom
docs/sidebar-theme-toggle

Conversation

@LimiNode

Copy link
Copy Markdown
Owner

Summary\n- move the Doxygen Awesome theme toggle into a dedicated header container\n- restore the full-width desktop sidebar search row with project-specific CSS\n- extend layout smoke coverage to wide desktop and assert search width/toggle placement\n\n## Validation\n- node --check for both custom scripts\n- git diff --check\n- Playwright smoke in publish workflow\n- full CI workflow

Move the Doxygen Awesome theme toggle into the documentation header, keep the search row full width, and assert the layout at desktop and mobile viewports.
Treat horizontal or vertical separation as non-overlap now that the theme toggle lives above the full-width search row.
Wait for the custom header container to own the dark-mode toggle before measuring the generated layout.
Relocate and deduplicate the Doxygen Awesome toggle before measuring the generated layout.
Allow the theme resize handler and custom relocation observer to settle before asserting generated page geometry.
Relocate the toggle immediately from mutation and resize handlers so the theme cannot leave it in the search row after layout changes.
Reconcile the custom header placement periodically so Doxygen Awesome cannot move the toggle back into the search row.
Print the measured toggle parent and geometry when diagnosing generated documentation layout in CI.
Validate the rendered header placement and dimensions instead of depending on a fragile parent id after Doxygen rewrites the header DOM.
Keep the generated documentation smoke test focused on stable placement and geometry assertions without temporary DOM diagnostics.
@LimiNode
LimiNode merged commit f6600b5 into main Sep 11, 2026
14 checks passed
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 this pull request may close these issues.

1 participant