Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibly better mobile support? #60

Open
SKCro opened this issue Feb 5, 2022 · 1 comment
Open

Possibly better mobile support? #60

SKCro opened this issue Feb 5, 2022 · 1 comment

Comments

@SKCro
Copy link

SKCro commented Feb 5, 2022

There should be better support for mobile browsers. I was planning to use this to browse the web on my old iPod touch, only to find I can't type anything into any text boxes because the keyboard won't show up. Granted, it's technically just sending images to a client browser and it relies on keyboard input, but it should have a keyboard trigger button that could be tapped after clicking on a textbox or something. Could it be possible to make it trigger a keyboard display when a textbox is selected, or maybe a keyboard trigger button that you use after clicking on a text box? What I'm thinking is implementing an invisible text box (triggered when clicking a textbox, or when clicking the keyboard trigger button, whichever you guys decide to implement) that just sends keyboard input to the browser, which passes it to the webpage.

Thanks!

@ttalvitie
Copy link
Owner

I have received a few requests like this before, however, my main focus in this project is in a bit older retro hardware, so I probably won't personally have time to advance touch screen device support any time soon.

Ideally, someone would create a replacement for the default Retrojsvice plugin that is specifically meant for newer client browsers like the one in iPod Touch. This is because Retrojsvice is designed to work with very old browsers like IE4, and thus adding new features to it without breaking compatibility is difficult. If you're interested, see the thread in issue #16 for more discussion on how to do this. The thread contains also some attempts to work around the problem (I haven't tested them).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants