History popup cropped on bottom
See original GitHub issueI found that my popups are cropped at the bottom, when their height hits the max-height:
It can be fixed by subtracting 60px in custom css:
.popup--tiles {
max-height: calc(100vh - 50px - 80px - 30px - 62px);
border: 1px solid red;
}
It’s easiest testable by opening a history popup on mobile and turning your phone to landscape. Both in Chrome and Firefox. I am pretty sure, this was correct when I migrated history popup to the modular popup.
Do you see this, too? Or is it some strange setting of mine, which I just didn’t find?
If it’s a real issue: why 60px?!
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Bottom of post popup is cut off in small screen resolutions.
I am getting this problem on ALL resolutions. I think I know whats going on. There have been shit loads of posts about...
Read more >android - PopupWindow goes out screen's bottom boundary
But when the item near the bottom of the screen the popup window is cropped(part of it outside the screen). How to get...
Read more >Instagram Story Hacks: 32 Tricks and Features You Should ...
These Instagram Story hacks will save you time and make you the best ... Then, paste in the cropped screenshot of your post...
Read more >How To Crop the Window Capture in OBS - Alphr
A pop-up window will appear. Click on the tiny “+” button in the lower-left corner. Find the “Crop/Pad” filter on the list and...
Read more >Configure pop-ups (Map Viewer Classic)—ArcGIS Online Help
Enter a caption for the chart. The caption appears below the title and above the chart. It is useful for giving a short...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m fine with adding some workaround for this.
Or maybe this approach mentioned in the article will work as well:
Seems a bit cleaner.
And whatever you do, consider browsers that don’t support
vh
and other new APIs and do it in a “progressive enhancement” way so that it helps new browsers but doesn’t break old ones.