This release adopts several improvements for mobile browser support. (Thanks to Dannii, Dan Fabulich, and vmiliantsei for suggestions.) The handling of the on-screen keyboard is much better now. Still not perfect though. The transitions when the keyboard pops up and down are ugly, but everything should wind up in the right place.
I’ve tested this heavily on iPad (iOS Safari, iOS Chrome, iOS Firefox) but not on Android or iPhones. So a certain amount of hammering would be welcome. The basic Advent.inf test is here, in a couple of layouts:
The HELP menu is a known sore point; you can get stuck in the menu and not be able to open the keyboard again. But outside of that, the game should be playable.
When you’re in that situation, can you scroll up to see the input line?
(I have code in there to automatically scroll up, but the browser is obstreperous and I had to do it in a hacky way to make it work on Safari. I guess I need to get even hackier on Android. But if you can still scroll down and keep playing, it’s not a critical failure.)
Parchment/AsyncGlk’s support for one-col templates is a little bit different: I expect the #gameport to be absolutely positioned relative to the <body>, and then any header or footer to be accounted for in the #gameport’s margins. This makes the height calculations really simple when the screen is resized. But it doesn’t really work with Zarf’s one-col template, because its #gameport is nested inside a few other <div>s. Of course it would be better if the two interpreters were fully compatible with all of Inform’s site templates. I should look into seeing if I can adapt my calculation to work in the one-col template.
Are they both available as website templates? Cause I can only see the one template zip on the Quixe page.
Another option would be to just release my own one-col template. I could even package it with Parchment (the next release of Inform 7 will mean that one Parchment extension could contain both the interpreter core, as well as other optional website templates.)
