hasadna
Annoying issue with iOS: keyboard is closing after every click
See the following GIF:
When clicking on buttons (even the send button), the keyboard closes, and then the user need to click the input again in order to get the keyboard.
I think catching the click event of the option buttons / send button and doing e.preventDefault(); will prevent it and keep it open.
Tested with latest iOS, iPhone 11 Pro Max, Safari browser.
@dotansimha can you check again (either on the live site or in our staging environment) to verify if your report is still relevant, following the recent releases?
Thanks @noamoss . In both staging and prod env, it's still closes the keyboard :(
@dotansimha
can you send here the unique url from https://whatismybrowser.com on the relevant device?
@akariv any way to leave the keyboard open when moving between two open questions?
not that I know of. The input box disappears between the questions.
On Sun, Apr 5, 2020 at 2:39 PM noamoss [email protected] wrote:
@akariv https://github.com/akariv any way to leave the keyboard open when moving between two open questions?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hasadna/avid-covider/issues/93#issuecomment-609402594, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5MPWPZHK4NOB4Q5TNTRLBUV3ANCNFSM4LTVKQ7Q .
@akariv any (theoretical) way to check from a wait clause what is the type of the next wait and leave the input field open? If that's possible we will turn this report into an open task for other developers.
Not really, as the next wait often depends on script logic. We might be able to leave the input open until there's another wait that is not textual, but that might happen after some time or not at all...
On Sun, Apr 5, 2020 at 3:24 PM noamoss [email protected] wrote:
@akariv https://github.com/akariv any (theoretical) way to check from a wait clause what is the type of the next wait and leave the input field open? If that's possible we will turn this report into an open task for other developers.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hasadna/avid-covider/issues/93#issuecomment-609408143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5M7GT4JLE6RNREEIA3RLB2BDANCNFSM4LTVKQ7Q .
@akariv I guess if e.preventDefault on relevant events won't work, maybe it's possible to create a hidden input and keep the focus on it while waiting across questions?
In which case the chat will continue running most of the time on half a screen with the keyboard open. Since there are about two cases where this is relevant (age-city-street and people-around-you) and we didn't get any other complaints about this, I think this is low priority and good candidate for an external contribution.
On Sun, Apr 5, 2020 at 3:49 PM Dotan Simha [email protected] wrote:
@akariv https://github.com/akariv I guess if e.preventDefault on relevant events won't work, maybe it's possible to create a hidden input and keep the focus on it while waiting across questions?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hasadna/avid-covider/issues/93#issuecomment-609411381, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5KSXOXN4R2MK5JRJGLRLB46HANCNFSM4LTVKQ7Q .
Btw, inputs should be autofocused and don't need to be clicked in order to open.