-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Chrome Feature Parity #1681
Comments
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!). |
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? |
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). |
My impression is that various architectural decisions have made SSL Documented here: On Tue, May 12, 2015 at 11:03 AM jsha notifications@github.com wrote:
|
Annoying, but not a big deal. Thanks for the info! |
Just trying to think what other differences there are... |
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? |
Now we use the same codebase for Chrome and Firefox. |
I thought there was an issue for this, but couldn't find it when looking... Are we ever going to get feature parity in Chrome vs FF? :)
The text was updated successfully, but these errors were encountered: