I opened the login screen and then turned on airplane mode before entering any credentials. The page remained visible but every field froze. After thirty seconds I turned airplane mode off. The fields stayed frozen for another few seconds and then became active again. No error message appeared and no refresh was required.
I entered the credentials and the dashboard loaded at normal speed. The balance and markets looked correct. The brief freeze during the network switch had not disturbed the login process itself.
What the freeze prevented
During the frozen period the password field refused any input. The page simply waited. Once the connection returned the field accepted characters immediately. I used matchexch 9 login for the test and completed the login only after the fields became responsive again.
A second test with credentials already typed
On the following evening I entered the password first and then switched airplane mode on. The page froze with the details still visible. Turning the connection back on allowed the login button to work without retyping. The session continued normally after that point.
Brief group notes about the airplane mode test
I described the freeze and the clean recovery. Two people replied that they had tried similar network interruptions. One said the page recovers faster on mobile data than on wifi. Another noted that any typed but unsubmitted details remain in place through the freeze. The comments stayed practical.
One precaution that remained after the tests
I no longer enter credentials while the network indicator looks unstable. Waiting for a solid connection before typing removes the short freeze entirely. The extra moment of patience keeps the login sequence uninterrupted.
Airplane mode produced a temporary freeze on the login screen and then released the fields cleanly when the connection returned. No data was lost and no new login steps were introduced. Once the behaviour was confirmed the possibility of a mid login network change became a minor detail. The match schedule continued to decide when the login screen needed to open next.