Repository navigation
Tighten elevation spacing and keep estimate guidance with results - #32
Merged
Merged
Conversation
Stanback
marked this pull request as ready for review
October 20, 2026 02:17
Stanback
force-pushed
the
fix/elevation-field-spacing
branch
from
October 20, 2026 02:17
539bf6a to
b7e7695
Compare
Stanback
enabled auto-merge (squash)
October 20, 2026 02:17
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.
The elevation label and unit toggle now sit 8 px above their input, instead of accumulating a grid gap and a bottom margin. Helper text explains the selected altitude policy without an unlabeled equivalent in the other unit.
The conversion estimate/entry reminder moves from the input form to valid course results, with the simpler wording “Converted times are estimates. Check your meet’s entry rules.” The widget uses the same wording. Native/MCP placement follows in the separate standards update.
Validation: Svelte/TypeScript has zero errors/warnings; 47 browser cases pass with one expected desktop-only skip, including desktop/phone altitude unit and policy checks. Updated screenshots inspected.
Follows the merged #31. National benchmarks and native/MCP guidance placement remain in the separate standards follow-up.