zimfarm
zimfarm copied to clipboard
openzim
Recipe free text search/filter became unusable (on iPad)
Thre recipe free text search/filter is since this morning (for me, on my iPad) unusable. It was working fine before. Reason is that each time I write (or remove) a letter, the virtual keyboard just disappear (because the input looses the focus). No problem with FF on Linux (works as usuable).
Do you have any idea how I can reproduce the issue? I do not have any iPad at home... Could you add information about OS + Browser version? If the issue appears any since this morning, I would suspect it is linked to some update of your device stack, nothing has been changed in Zimfarm. Could you try another browser on you iPad?
@benoit74 you will need an iOS. Somehow it seems Firefox specific, as it works with Safari. My version of FF is Firefox 116.2 (33536) with iOS 16.6. Beside this input problem it works everywhere properly. @rgaudin Do you have the same problem with your iOS device?
I do. I have the very same iOS and FF versions (iOS update dates a couple days ago I think). This field as an onchange event handler to automatically update the list of recipes based on input.
onchange should not be fired everytime a key is pressed but that might be a bug here.
Or, we could have another thing interfering and requesting the focus.
Since @benoit74 doesn't have an iOS device, I'll look into it.
@kelson42 the problem is that onchange (each char), we query the API and update the UI ; but this has no impact.
What we also do is that we update the URL (to add/update the ?name=xxx) and this is done via $router.replace() and for some reason this now hides the keyboard on FF for iOS. It's not a loss of focus, the input field still has the focus, but the keyboard is hidden.
Given it's only impacting this special browser (Firefox running on WebKit) in a very recent update and because there's no obvious easy fix, I went the hack way and disabled the URL update for FF on iOS.
Maybe we should keep that open to revisit later…
@rgaudin OK, lets wait a bit if the bug will be fixed. Otherwise we might have to report the bug to Mozilla.