I am not the person who originally asked for this, but I’d want to scan my eyes over conditions:
* with and without the keyboard focused,
* in each of the preference states (e.g. tab bar vs single tab for iOS, which influences whether there’s a compact address/button bar on the bottom or an address bar at top plus a button bar at bottom), and
Thanks for this @alwa. It definitely helped me better understand the question. I commented below @doctorpangloss but agreed: portrait/landscape mode are vital, and that's already on our roadmap.
This is like that scene in Star Wars where Luke asks questions and Yoda just closes his eyes, fades away and dies.
This is meant as a light hearted question: how could you have gotten this far making a viewport tester and the mobile website development journey without understanding and dealing with the most important and disruptive behavior in mobile viewports? Like I get that this is just a free project and it does what it does.
Haha funny analogy. What you and @alwa said makes sense: thanks for sharing that. It's related to Caveat #1 I mentioned above, but I like the idea of being able to toggle on/off the header/footer, to simulate real-world scrolling behaviour. I got that added to our list.