search

Igalia / wolvic

A fast and secure browser for standalone virtual-reality and augmented-reality headsets.
https://wolvic.org
Mozilla Public License 2.0
802 stars 102 forks source link

External keyboard (Bluetooth and USB) not recognised by browser window #1141

Open kierannolan opened 10 months ago

kierannolan commented 10 months ago

Configuration

Wolvic version: 1.5.1 Wolvic build ID: Meta store version

Hardware: Meta Quest 3

Steps to Reproduce

  1. Can type into the URL bar, but the browser window itself isn't responding to keyboard interactions

Current Behavior

No response from the browser window to key inputs

Expected Behavior

Feedback from keyboard inputs

svillar commented 10 months ago

Is it working fine in other apps or just Wolvic?

kierannolan commented 10 months ago

It works in the Meta browser but not Wolvic.

Here's a link to a sample scene on Glitch.me for test purposes, try it out in immersive mode: https://aeolian-tide-shock.glitch.me

( also code link is here.)

If you can implement in-scene keyboard access please it would be a huge help.

pt1997 commented 9 months ago

The keyboard inputs are recognized when you click on a text filed on a side, then you can also use "Shift"+"Arrow-keys" to select text. In this situation, the Volume control buttons on the headset don't work anymore.

I think this might be connected. It appears as if all input either goes to the page or to the application. If this is the case, this would need to be changed to make keyboard shortcuts like ctrl+tab, ctrl+f, F6, ... useable.

(probably part of #1096 ) In addition, the following would be very useful to find the keyboard and the keys. https://developer.oculus.com/documentation/native/android/mobile-physical-tracked-keyboard/

boutell commented 9 months ago

I am also experiencing this issue. As @pt1997 points out, interacting with a text field allows use of the keyboard, but this does not account for applications like vscode.dev / code server (web-hosted Visual Studio Code) that rely on access to keyboard events any time the browser window has the focus. For me that means Wolvic is not currently an option as a productivity browser, which is a pity because it is more flexible than the Meta browser in other ways, and the ability to log into a Firefox account and use Firefox extensions is huge.

I'll also note that even when working with a text field you just selected, putting down your hand controllers usually results in a loss of keyboard focus, either right away or after a few seconds.

For comparison, the Meta browser supports keyboard events at all times.

Wolvic also doesn't appear to support a mouse pointer, which is supported both on the main Quest desktop and in the Quest browser.

boutell commented 9 months ago

Of course I realize this is an open source project. Just a thought, is there a way to chip in financially toward particular features?

pt1997 commented 9 months ago

@boutell I don't know about this, but you can donate here https://opencollective.com/wolvic

boutell commented 9 months ago

Thanks. I made a small contribution, just because I like the project.

kierannolan commented 9 months ago

I've sent one through just now too, thank you Wolvic team for your great work

On Tue, 16 Jan 2024 at 17:40, Tom Boutell @.***> wrote:

Thanks. I made a small contribution, just because I like the project.

— Reply to this email directly, view it on GitHub https://github.com/Igalia/wolvic/issues/1141#issuecomment-1894211829, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKQ5QRCKAGODC7BRN7F5S3YO23RVAVCNFSM6AAAAABAGXQBQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGIYTCOBSHE . You are receiving this because you authored the thread.Message ID: @.***>