Improve mobile calendar presentation and Caelus header alignment - #36
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Center the Caelus header and align its top edge with the close button, with spacing to prevent overlap on phones. Reorder mobile BD Cal tiles to Calendar, Summary/Plantings/Notes, Moon Attributes, Planetary Aspects, Twelve-Month Overview, and the BD Cal icon while retaining the desktop tile layout.
Arrange the BD Cal header into three centered lines: title; date/time; Report, coordinates, and Theme. Update the version to
v0.26.275.3.Verification
npm run validate:pr: all 50 Playwright Chromium checks passed on the final changes.git diff --check: passed.Contributor checklist
Maintainer verification
npm run validate:prpasses on a trusted host.Residual risk or unverified areas
Physical mobile devices and non-Chromium browsers were not tested. Hardware, MQTT, and onboarding paths were not exercised; changes are limited to presentation and the version marker.