Punch nazis, trebuchet TERFs.

I am building Voyager, a client for lemmy!

  • 48 Posts
  • 756 Comments
Joined 2 years ago
cake
Cake day: April 15th, 2024

help-circle
  • This is a lemmy issue - lemmy doesn’t have customizable report reasons. “Breaks community rules” = mods should handle, “spam or abuse” = admins should handle. I’m open to better alternatives but they should make it clear whether admins or mods should handle, and they should have some prefilled options (not everything should be custom response)















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




  • aehardingMtoVoyager@lemmy.worldVoyager semi broken from outdated webview
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 months ago

    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.