You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Want to break out the specific feature differences here so we can start prioritizing? There are some features, like SSL Observatory, that may never be possible on Chrome, but I definitely would like to bring them to feature parity (and similar UI!).
I'm not positive SSL O would be WONTFIX in Chromium. Historically that team has been very against any extension change the HTTPS trust mechanics, but I think has been tentatively open to letting extensions read certificate data about pages (but not modify).
I'm not positive SSL O would be WONTFIX in Chromium. Historically that
team has been very against any extension change the HTTPS trust mechanics,
but I think has been tentatively open to letting extensions read
certificate data about pages (but not modify).
—
Reply to this email directly or view it on GitHub #1681 (comment)
.
Will this change with the Firefox Web Extensions API? From what I understood they are going to deprecate the current API and then move to WebExtensions API which is compatible with Chrome with minimal changes.
Or does it remove SSL Observatory also from Firefox? If it's coming, will it also have the option to use Tor?
Activity
jsha commentedon May 12, 2015
Want to break out the specific feature differences here so we can start prioritizing? There are some features, like SSL Observatory, that may never be possible on Chrome, but I definitely would like to bring them to feature parity (and similar UI!).
reedy commentedon May 12, 2015
Yup, I can do. Keep this as a semi tracking ticket for the whole lot?
I wonder if for stuff like the SSL Observatory we could upstream it to Google/Chromium? Are these likely to be WONTFIX then upstream?
jsha commentedon May 12, 2015
I'm not positive SSL O would be WONTFIX in Chromium. Historically that team has been very against any extension change the HTTPS trust mechanics, but I think has been tentatively open to letting extensions read certificate data about pages (but not modify).
zmanian commentedon May 12, 2015
My impression is that various architectural decisions have made SSL
observatory capability in the Chrome APIs complex to implement.
Documented here:
https://code.google.com/p/chromium/issues/detail?id=107793
On Tue, May 12, 2015 at 11:03 AM jsha notifications@github.com wrote:
reedy commentedon May 12, 2015
Annoying, but not a big deal. Thanks for the info!
reedy commentedon May 12, 2015
Just trying to think what other differences there are...
Mikaela commentedon Sep 3, 2015
Will this change with the Firefox Web Extensions API? From what I understood they are going to deprecate the current API and then move to WebExtensions API which is compatible with Chrome with minimal changes.
Or does it remove SSL Observatory also from Firefox? If it's coming, will it also have the option to use Tor?
gloomy-ghost commentedon Nov 6, 2017
Now we use the same codebase for Chrome and Firefox.