r-zakarya
bde22d2288
The frame is nailed to the whole screen, so when the keyboard rises the content overflows nothing and the bottom third becomes unreachable: the form's password field could only be seen by folding the keyboard away. Reserving below the scroll area exactly the height the keyboard covers gives the panel something to scroll. The measure answers correctly whether or not the engine actually resizes the window - if it does, innerHeight shrinks too, the reserve is zero, and the natural overflow already does the work. No need to know which case applies. A first attempt shrank the body to the visible height; it changed nothing observable, and it depended on which of three over-constrained box properties the engine drops. This does not. The plan records where a save's time actually goes: 46 ms of crypto, 2745 ms of PUT for 267 Ko. That is the floor for a monolithic container.
