Hey thanks! ^^

Dunno how I missed this so long! Thanks for originally reporting.

I forgot I received this a few years ago from volunteering… let’s go Artemis!

608? That’s my area code 😆

@return2ozma@lemmy.world you are appreciated!!

You can export settings and import, should include tags.

Posted from my 2m aliexpress usb-c cable running at 40gbps

Awesome thanks!

What version of Voyager? You can check in Settings -> About

And please do feature detection

I’m not sure how you’d do that with safe area insets. You could check for zero but some modern devices megitimately have zero safe area insets. Capacitor itself has to check Blink version for the SystemBars plugin.

But the app works fine with a “too old” webview. Why warn about it?

If you go into dark mode the status bar will be white with white text, because safe area doesn’t work properly.

And or tauri

You dont need the Android System Webview in particular. Android supports alt webviews. The important part is to make sure its based on Blink 140 or newer (haven’t tested other engines).

Gotta keep your webview up to date! There’s alternatives as described in the comments but yeah, having a version of Chromium older than a year old is pretty dangerous/insecure.

I think most ‘normal’ android users never really think about it because Google keeps their webview up to date automatically, but if you dont use Play Store this can be easily overlooked. Really important for device security though.

Edit: As for why Voyager requires System WebView >= 140… Android recently overhauled safe area insets and thei rollout was kinda botched with poor backward compatibility. This is a side affect unfortunately.

Using pop/cosmic here, is awesome!

I think that’s a bug with the piefed API. There is a bug on Github, just have to make the Piefed devs aware.

Great thanks

Thanks!

What version of android are you on?

What version on android are you running?

The new version of Capacitor has a totally new way of handling safe area and insets so I’m hoping this is resolved with that work!

I think that should be supported via the API in Lemmy v1