When using Dynalist in Safari on iPadOS, Dynalist will zoom (sometimes to very large sizes) when switching back to Safari from another app.
Latest iOS ā 13.4.1
Itās very hard to consistently reproduce, but it sometimes happens when swiping between apps, sometimes when using the app switcher, sometimes when using cmd-tab. Dynalist is effectively unusable when this happens.
The only way to fix the problem is to log out of Dynalist, close the Safari tab, navigate back to Dynalist, and log in again. The problem might re-occur almost immediately, however.
Iām having a hard time imagining something we did could cause this. Any chance youād run into this same bug on other websites in safari?
Iām also surprised that you have to log-out and log-in! Does it not fix itself it you relaunch safari by killing the app, or just close the tab and open a new one?
I did a little testing on our development iPad (13.4.1) and on Safari I canāt seem to get the zoom to happen unless I zoom in manually - If I do that I can still zoom back out with two-finger pinch. Not sure why that happens in your case but I suspect it might be Safari bug. Iām hoping Apple could fix it on their end on the next iOS version update.
Could be. It can happen when there has been no touch interaction at all, with everything going through a trackpad, and I certainly never pinch to zoom.
Itās very difficult to reproduce consistently, but it happens often enough that I KNOW it will start occurring at some point in a session.
I seemed to have reproduced it, still not sure why but I think itās caused by some kind of ānewā Safari feature, which āzooms inā to what it thinks is the article width youāre trying to read.
Iāve added a new tag to the page to force safari not to auto-zoom, while still allowing manual zooms. A quick test shows itās fixed! Will be deployed in the next few days.
Given youāre using the web version of Dynalist in Safari, there isnāt a version number you can check. Sorry about that - hopefully youāll find it magically fixed in a few days! (In the meantime I found that you can scroll to the left where the file pane is, then zoom back out using two-finger pinch gesture on the left pane)
I used Dynalist in Safari on iPadOS for about 30 minutes earlier and didnāt encounter the problem! Did I just get lucky, or was this the fix in action?
I think Iām on the latest build ā I have word count linked to zoom level.
Donāt know if this is just todayās quirk, but the problem has reversed ā the zoom is getting smaller each time I navigate away from, then back to, Safari.
I logged into Dynalist this morning with the express purpose of testing this, so that I could give you the clearest feedback possible.
It seems that there is no reliable way to reproduce the problem, but it will occur at some point in an extended use session. The change in zoom level can be triggered by:
Switching to another app and back again (swipe/app switcher/tab switcher).
Switching to another Safari tab and back again.
Switching to a different Dynalist file.
It happens in portrait and landscape, with touch or with keyboard/trackpad.
When Dynalist is affected, other non-Dynalist tabs are not (including this one, the forum, or the Dynalist log-in page). I have tested this with many tabs open.
I usually view Dynalist at 75% or 85% (using the AA button in Safariās address bar) as the default is too big. Itās possible that this is the root of the problem, but itās the only way to make Dynalist useful on an 11ā screen. I have been unable to replicate the problem when using Dynalist at 100% on a fresh load.
Maybe the answer is just to make the default view smaller. 85% is comfortable, but 75% is probably even better.
I hope this information helps you to narrow the problem down. Iām all-in on both Dynalist and iPad, so having the two work together seamlessly would be incredibly usefulā¦
I donāt want to jinx things or divert your efforts to fix the problem. but since I wrote my last message early on Saturday morning the problem has not resurfaced. I used Dynlist in Safari on my iPad extensively on Saturday and Sunday and did not encounter the problem once.
Maybe I just got lucky, or maybe Iām using a newer build without knowing it. I just thought you should know. Iāll post here again if the problem happens again (I know Iām tempting fateā¦)