webbrowser-app

  1. Bug #1355120
  2. Comment #5

Comment 5 for bug 1355120

Revision history for this message
Olivier Tilloy (osomon) wrote :

> Now, can this warning be surface in the current state of things, or do we
> need that SSL Status API?

We’ll need the SSL status API indeed (and a way to allow insecure content to be loaded over a secure connection, if it’s not already exposed in the preferences).