I mostly solved both problems. Looking at the difference between code generated by betza.js and betzaNew.js, I saw that the latter included the style "aspect-ratio: 10 / 11" for the board. To test whether this was the problem, I added this CSS to this page:
#board0 {aspect-ratio: auto !important}
When I loaded the page on my iPad, it no longer had the problem with extra space showing up. As a further test, I commented out line 108 in my fork, and I loaded pages that used it on my iPad. This fixed the problem on Firefox and Edge, though not on Chrome and Safari. Maybe it's a caching issue with these two, though I did try clearing the browser cache without it helping, and the script was called with the query string "?nocache=true".
While using the iPad, I noticed that I could click on a piece in the Pieces table and click where I wanted it to go in the diagram. I tried this on my Android tablet, and it worked. Although dragging is not working, it's enough to have an alternative to dragging that will work.
I mostly solved both problems. Looking at the difference between code generated by betza.js and betzaNew.js, I saw that the latter included the style "aspect-ratio: 10 / 11" for the board. To test whether this was the problem, I added this CSS to this page:
When I loaded the page on my iPad, it no longer had the problem with extra space showing up. As a further test, I commented out line 108 in my fork, and I loaded pages that used it on my iPad. This fixed the problem on Firefox and Edge, though not on Chrome and Safari. Maybe it's a caching issue with these two, though I did try clearing the browser cache without it helping, and the script was called with the query string "?nocache=true".
While using the iPad, I noticed that I could click on a piece in the Pieces table and click where I wanted it to go in the diagram. I tried this on my Android tablet, and it worked. Although dragging is not working, it's enough to have an alternative to dragging that will work.