It would enhance the user experience if pressing the Enter key on both PC and mobile devices triggered the search function, instead of requiring a manual tap or click on the search button.
It would enhance the user experience if pressing the Enter key on both PC and mobile devices triggered the search function, instead of requiring a manual tap or click on the search button.
I'm not understanding this, the Enter button should already trigger search when press on desktop and mobile devices.
I'm not required, on my end, to manual tap the "Search" button.
I'm not understanding this, the `Enter` button should already trigger search when press on desktop and mobile devices.
I'm not required, on my end, to manual tap the "Search" button.
My instance is 4get.turtlecute.org. I also tested on the official 4get.ca, and it doesn't work there either. Could it be keyboard or Android browser related?
I'm testing it on Vanadium (hardened Chromium) with the Heliboard keyboard.
My instance is 4get.turtlecute.org. I also tested on the official 4get.ca, and it doesn't work there either. Could it be keyboard or Android browser related?
I'm testing it on Vanadium (hardened Chromium) with the Heliboard keyboard.
I've tested with Firefox, specifically Iron Fox using the default keyboard that comes with LineageOS.
You could try a different keyboard or browser, then narrow it down what's causing the issue. I don't think it's a 4get issue?
I've tested with Firefox, specifically Iron Fox using the default keyboard that comes with LineageOS.
You could try a different keyboard or browser, then narrow it down what's causing the issue. I don't think it's a 4get issue?
I'm aware of the issue, but I'm unable to see the javascript console on mobile devices. If you manage to share the error logs I will be able to fix the problem.
From my testing, it seems to happen on old browsers, I need to figure out why.
I'm aware of the issue, but I'm unable to see the javascript console on mobile devices. If you manage to share the error logs I will be able to fix the problem.
From my testing, it seems to happen on old browsers, I need to figure out why.
I'd like to help but i don't know how could i check these kind of errors, if i export a logcat of the app on android i don't think it catches these kind of things.
Nvm, thank a lot for your time and work anyway 🙏
I'd like to help but i don't know how could i check these kind of errors, if i export a logcat of the app on android i don't think it catches these kind of things.
Nvm, thank a lot for your time and work anyway 🙏
I'm aware of the issue, but I'm unable to see the javascript console on mobile devices. If you manage to share the error logs I will be able to fix the problem.
From my testing, it seems to happen on old browsers, I need to figure out why.
Are these also old Firefox-based browsers? You may be able to use about:debugging#/setup in a Firefox browser on desktop, which allows you to open the developer tools for the mobile browser.
> I'm aware of the issue, but I'm unable to see the javascript console on mobile devices. If you manage to share the error logs I will be able to fix the problem.
>
> From my testing, it seems to happen on old browsers, I need to figure out why.
Are these also old Firefox-based browsers? You may be able to use `about:debugging#/setup` in a Firefox browser on desktop, which allows you to open the developer tools for the mobile browser.
Are these also old Firefox-based browsers? You may be able to use about:debugging#/setup in a Firefox browser on desktop, which allows you to open the developer tools for the mobile browser.
I've this problem o Vanadium (it's a very recent chromium based mobile browser)
> Are these also old Firefox-based browsers? You may be able to use `about:debugging#/setup` in a Firefox browser on desktop, which allows you to open the developer tools for the mobile browser.
I've this problem o Vanadium (it's a very recent chromium based mobile browser)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It would enhance the user experience if pressing the Enter key on both PC and mobile devices triggered the search function, instead of requiring a manual tap or click on the search button.
I'm not understanding this, the
Enterbutton should already trigger search when press on desktop and mobile devices.I'm not required, on my end, to manual tap the "Search" button.
Sorry, my mistake. It works on desktop but not on Android (it doesn't work for me and many of my instance users).
This is working on Android for me on the official 4get instance and my own instance.
Can you provide me the URL to your instance?
My instance is 4get.turtlecute.org. I also tested on the official 4get.ca, and it doesn't work there either. Could it be keyboard or Android browser related?
I'm testing it on Vanadium (hardened Chromium) with the Heliboard keyboard.
I've tested with Firefox, specifically Iron Fox using the default keyboard that comes with LineageOS.
You could try a different keyboard or browser, then narrow it down what's causing the issue. I don't think it's a 4get issue?
I'm aware of the issue, but I'm unable to see the javascript console on mobile devices. If you manage to share the error logs I will be able to fix the problem.
From my testing, it seems to happen on old browsers, I need to figure out why.
I'd like to help but i don't know how could i check these kind of errors, if i export a logcat of the app on android i don't think it catches these kind of things.
Nvm, thank a lot for your time and work anyway 🙏
Are these also old Firefox-based browsers? You may be able to use
about:debugging#/setupin a Firefox browser on desktop, which allows you to open the developer tools for the mobile browser.I've this problem o Vanadium (it's a very recent chromium based mobile browser)
If you can attach a debugger and show me the error in the javascript console I can help.