Skip to content
This repository has been archived by the owner on Nov 6, 2023. It is now read-only.

Chrome Feature Parity #1681

Closed
reedy opened this issue May 12, 2015 · 8 comments
Closed

Chrome Feature Parity #1681

reedy opened this issue May 12, 2015 · 8 comments

Comments

@reedy
Copy link
Contributor

reedy commented May 12, 2015

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? :)

@reedy reedy added the chrome label May 12, 2015
@jsha
Copy link
Member

jsha commented 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
Copy link
Contributor Author

reedy commented 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
Copy link
Member

jsha commented 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
Copy link

zmanian commented 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:

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

@reedy
Copy link
Contributor Author

reedy commented May 12, 2015

Annoying, but not a big deal. Thanks for the info!

@reedy
Copy link
Contributor Author

reedy commented May 12, 2015

Just trying to think what other differences there are...

@Mikaela
Copy link
Contributor

Mikaela commented 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
Copy link
Collaborator

Now we use the same codebase for Chrome and Firefox.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants