Stephen Power

In my case, I needed to use the Cargo syntax to specify that only a specific version can be used. I would also recommend deleting `Cargo.lock` and cleaning your `target`...

Apologies, I should've specified that my problem wasn't the fault of `wasm-bindgen`. There is a high possibility that I did something incorrectly so maybe it wasn't a Cargo bug. As...

>This is actually not needed, the current error message tells you how to fix this probably in a better way: ```cargo update -p wasm-bindgen --precise x``` This did not work...

Yeah, it is happening in both Epiphany and in the Linux Tauri app which uses [`webkit2gtk-rs`](https://github.com/tauri-apps/webkit2gtk-rs). Why is webkit so bad? Oh right, Apple... Anyways, I'll take a closer look...

Fair point, the webkit and webkit2gtk/linux issues are just very cumbersome. Checking the decoder, it gives `avdec_h264`. Using the following command still does not fix the issue: ``` export GST_DEBUG=videodecoder:5...

Using the following also still gives a green screen: ``` export GST_PLUGIN_FEATURE_RANK=vah264dec:max,vavp9dec:max && cargo tauri dev ```

That might be the issue: ``` No such element or plugin 'vah264dec' ```

After installing `gst-plugin-va` via `yay -S gst-plugin-va` and doing a `cargo clean`, it still gives a green screen. The result of `gst-inspect-1.0 vah264dec` is: ``` Factory Details: Rank none (0)...

Yep, I checked the environment vars using: ``` $ env ``` It gives: ``` GST_PLUGIN_FEATURE_RANK=vah264dec:max,vavp9dec:max // other env vars ```

How many subscriptions do you have? Have you tried changing your Invidious instance in the top right? The UI needs to show a placeholder when the import is successful and...