3 ms·
Some issues on the front page: • The height of the #use-case element can vary (for many mobile-sized displays, “locate nearby caffeine” takes two lines, unlike
by chrismorgan 9y ago
Some issues on the front page:
• The height of the #use-case element can vary (for many mobile-sized displays, “locate nearby caffeine” takes two lines, unlike the rest which are one line), which messes up the scroll position regularly when you’re below it. A solution is to take the longest, have it there for layout with `visibility: hidden`, and have the actual text at the same point, but with `position: absolute` so that it doesn’t contribute to layout.
• .cc-window (the stupid cookie banner) has z-index: 9999 but #action has z-index 99999 which is higher, but should probably be lower. (Else it blocks the “Got it” button.)
• That map sure took a long time to load. Fifteen, thirty seconds for initial render (high-DPI display, Firefox, Australia). Apparent indefinite hang for some tiles when I was interacting with it so that I just gave up on it after a minute or two. Sometimes it worked better after a reload.
- stadiamaps 9y agoThanks for your feedback Chris! We'll look into those display issues right away. We pushed a new design before the HN post took off, and we clearly missed a few details. Regarding map load time, our servers are currently located in the US (which is where all of our paying customers are based at the moment). We do have multiple servers running in a cluster, but we are still working on our geographic diversity. While our load times are generally good wherever we've tested in the northwestern hemisphere, my cofounder lives in Korea now and he is acutely aware of our latency spikes in Asia. Our CDN, CloudFlare, routes traffic based primarily on peering arrangements until you start paying them a lot more, but we're working on geographically diversifying our server fleet behind CF load balancers as our next step.