possible fix for occluded height #449
Merged
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.
ideally, TSML UI will at a minimum fill the available space on the screen
when it's in list view, it typically scrolls higher than the viewport and that's fine
when in map view however, it can sometimes be too small or too big. a recent PR set the min-height to be 100dvh, which is great except when there's a fixed element, such as a header, occluding part of the viewport
check out https://aasanjose.org/meetings?view=map - ideally the map would not go off the bottom of the screen
this PR computes the height of probably-occluding elements and adjusts TSML UI's min-height accordingly. also adds example test with a fixed header
concerns: