That’s a good one. Thank you for the tip, I’ll add those options to the template.
You can try adding
<hr id="answer">
as the first line on the back (before <div id="backwrap"...). And the following CSS on the styling tab to hide the appearing horizontal line:
#answer {
margin: 0;
border: 0;
}
The backside doesn’t appear scrolled down neither on desktop nor in AnkiDroid for me (no matter how many extra fields I put on the back and keys on a card keyboard), so I can’t tell for sure if this would work, especially on iPhone, but should be worth a try.
That’s probably because Safari does not support svg images in css (and I guess Anki Mobile uses the same web engine on iOS):

The same issue is likely the cause for the audio buttons looking wrong as well.
One can of course put the image inside the HTML template itself, but I’m not sure fixing a cosmetic issue on a single platform is worth complicating the template for everyone. Maybe iOS web engine will catch up with the rest of the browsers at some point. But if you’d still like to have that hint button icon right away, I can suggest several alternative ways to put it in.
There is a couple of other things that look different that I notice. If you don’t mind, could you test several styles to try and make the template appear normally?
- The first issue is with the centering of items on the info screen (back of a card). There shouldn’t be any support issues with it on iOS, so maybe it is simply gets overwritten by some default styles not present on other platforms. To enforce the styling you will have to find the following part on the styling tab:
and put.card-content { align-items: stretch; ⋯!importantat the end of the CSS descriptor:
If it doesn’t work, you could add a completely new different rule (anywhere on the styling tab, outside of any existing rules):.card-content { align-items: stretch !important; ⋯.card-content.back { align-items: start; } - The second issue is with the input line becoming semi-transparent after answer submission (it doesn’t do that on other platforms). To fix this I suggest you try adding the following rule:
#typeans:disabled { opacity: 1 !important; }

