Vault search doesn't work in Oculus Browser

[ian471]

Steps To Reproduce

1. Don a Quest or Quest 2 headset
2. Open https://vault.bitwarden.com/ in Oculus Browser
3. Log in
4. Select the "Search Vault" field with the controller
5. Using the virtual keyboard, enter a search term

Expected Result

Vault entries are filtered by search terms.

Actual Result

The full list of vault entries continues to be displayed.

Additional Context

Oculus Browser is based on Chromium (https://developer.oculus.com/documentation/oculus-browser/) but I can't repro the issue on Android with the mobile Chrome browser app.

This issue seems specific to the virtual keyboard. Using a PC keyboard via remote debugging works correctly.

This led me to view the keyboard events that are sent with each method.

Using the virtual keyboard:

Via remote debugging:

Note that the virtual keyboard doesn't send keydown, keypress or keyup events. Instead, it sends compositionupdate and compositionend.

I suspect the BitWarden web vault page may be listening for key* events to know when to react to changes to the search field.

Operating System

Android

Operating System Version

Oculus Quest OS 37.0.0.147.110

Web Browser

Chrome

Browser Version

Oculus Browser 19.1.0.1.50.350517500 ; Chromium 96.0.4664.174

Build Version

2.26.1

[Hinton]

Hmm this seems interesting. We are using the regular https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/input_event. As seen in https://github.com/bitwarden/web/blob/master/src/app/vault/groupings.component.html#L21.

This seems more like a bug with either Angular or with the Oculus browser. Will need to dig a bit deeper to figure out how Angular handles (input) events. Perhaps listening to changes on the model would work, slightly tricky to test though.

[ian471]

There doesn't seem to be anything special about BitWarden's usage of (input). I can try to provide a more complete dump of the Events Oculus Browser is emitting, and I'm happy to test fixes.

[Malachiel87]

I would like to see it too, for now is usable by sidequesting and put it as 2° window, it with copy/paste, but would be a good idea to make it a official app for meta :) i believe it don't require so much work, also you can add support to this browser too (it was the ex Mozilla VR browser) https://www.meta.com/it-it/experiences/5917120145021341/ https://www.wolvic.com/en/ And same, i will be happy to help to test and debug