useKrispNoiseFilter: Rely on Webkit version rather than Safari version for compatibility

[konsalex]

Select which package(s) are affected

@livekit/components-react

Describe the bug

We are building Hopp and rely on Livekit audio inside a Tauri application.

We just wanted to use Krisp noise removal hook, but we get:

LiveKit-Krisp noise filter is not supported in this browser

After digging a bit deeper to the transpiled code of @livekit/krisp-noise-filter, I think I found the issue. The version check if only on Safari versions, but not Webkit versions.

There is WASM support in the Webkit right now, but the version detected is 1.1 (for Safari) thus Krisp is not starting.

Reproduction

Start a dead simple Tauri app, try to import and use the Krisp SDK, or run the validation logic.

Logs

System Info

System:
    OS: macOS 15.5
    CPU: (10) x64 Apple M4
    Memory: 26.10 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.local/state/fnm_multishells/5194_1749131512949/bin/node
    Yarn: 1.22.22 - ~/.local/state/fnm_multishells/5194_1749131512949/bin/yarn
    npm: 10.2.3 - ~/.local/state/fnm_multishells/5194_1749131512949/bin/npm
  Browsers:
    Brave Browser: 137.1.79.119
    Chrome: 137.0.7151.69
    Safari: 18.5

Severity

serious, but I can work around it

Additional Information

No response

[lukasIO]

we cannot use webkit version parsing as the versions are stale, see webrtcHacks/adapter#1127 (comment).

[konsalex]

@lukasIO did not know that. Could there be another case, maybe a user provided flag to bypass the isSupported and then see if it breaks (EAFP style)?

Thinking what should be the strategy to work in environments like this, were Webkit would actually support Krisp, but there is a false negative.

[lukasIO]

I know this isn't ideal, but I think the easiest solution would be for you to spoof the user agent to include the Safari version

[lukasIO]

had another look at this, it would be nice for this to be detected automatically somehow, especially because some other features also rely on safari version checks.

However it seems for tauri you're only left with passing in your own custom user agent here https://v1.tauri.app/v1/api/config/#windowconfig.

This would be recommended so that also the underlying livekit-client SDK can parse the user agent accordingly