Chrome not proceeding with Web Integrity API deemed by many to be DRM - eviltoast

The Chrome team says they’re not going to pursue Web Integrity but…

it is piloting a new Android WebView Media Integrity API that’s “narrowly scoped, and only targets WebViews embedded in apps.”

They say its because the team “heard your feedback.” I’m sure that’s true, and I can wildly speculate that all the current anti-trust attention was a factor too.

  • Calavera@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    No, I’m not talking about default browser but the WebView app. For example I’m using Voyager for Lemmy, and if I click on this post’s link it will open the website in the WebView, then I can click to Open with firefox.

    But WebView itself is still chrome as you can see

    • flamingarms@feddit.uk
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Ohhhh I see. Yeah, I think Sync uses Chrome too. Sync has an option to always open links in external web browser, so that’s how I got around that.

    • Trainguyrom@reddthat.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      It’s even crazier than that. On some versions of Android there is no webview, only chrome! I think that was around Android 8 or so they dropped webview then re-added webview in the next version

    • aeharding@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      You can customize Voyager to open links in default browser not in-app: Settings -> General -> Open Links in