We are creating a FMX application using Delphi XE8 for Android set-top-boxes. The interface is done via webbrowser through keyboard arrows (remote control). The keyboard navigation (using jquery) works perfectly on the default Android's browser (4.4.2). When using TMS webbrowser component in our app the keyboard navigation brakes down - no hover effect and stops on any anchor. Javascript runs ok on the page - the only thing not working properly is the keyboard navigation.
Any clues?
Thanks.
Hi,
TWebBrowser works just like TTMSFMXWebBrowser. I know that is not a TMS issue but I was wondering if anyone encountered this problem before. Thanks.
UPDATE: I have just updated to Berlin and the webbrowser works ok now with the keyboard. However TTMSFMXWebBrowser (latest version to date) still doesn't work properly in Android when navigating from the keyboard.
Hi,
Can you perhaps provide additional information on how to reproduce this issue?
I can give you the link of our website on a private message (but it seems that PM is disabled) or to an email address (the site is not ready for public use).
Steps to reproduce:
- make a new application, add twebbrowser and compile on Android. An Android device with keyboard will be required in order to test the keypresses.
- make a new application, add tmswebbrowser and compile on Android.
The stock webbrowser will handle correctly the keypresses (through javascript) while TMS webbrowser will provide basic navigation without javascript.
Thank you.
Sent. Thank you.
Hi,
Open the link in a regular browser on a computer. You will notice that you can navigate through the site with the arrow keys from the keyboard. You can choose whatever movie you want or scroll down to live tv etc - all from the keyboard.
This kind of navigation will not work when you open the page on a tms browser from Android and using the keyboard arrows. It will work however just like the regular desktop browser if you use twebbrowser fom Berlin.
Thanks.
Hi,
Thanks for the code. Have tried it and the result is the same as before.
Hi, while further investigating this we get a 403 navigating to the URL you have sent us.
Sorry about that. Shuld be ok now. Thanks.
I'm still getting a 403, refreshed 5 seconds ago