Should be fixed in the next release. Sorry about that!

What device are you on? TIA!

Edit; if you could take a screen capture too would be very helpful!

I usually tap a comment, click share, copy link, then go to search tab and paste the url. Tap the comment and then see the context of the thread.

Its roundabout but also pretty rare flow, at least for me.

Good to hear. Added experimental support to the latest beta!

What version of Android are you running?

If you long press community name you can block from feed. Same with usernames!

Ah, lemmy.ml issue, I think I can fix that.

Interesting request! Although I don’t think SFSafariViewController allows clearing cookies by website

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

608? That’s my area code 😆

@return2ozma@lemmy.world you are appreciated!!

You can export settings and import, should include tags.

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.

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 their 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.

It shouldn’t ever do that pasting into the app. Maybe @FuyuhikoDate@feddit.org is on an old version of Voyager?

If you ever see a vger.to link get pasted into a comment you’re composing on Voyager lmk. It should always be stripped out. If it isn’t, there is a bug.

Great thanks

Thanks!