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

Chrome Feature Parity #1681

Closed
Closed

Description

@reedy

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

Activity

  1. jsha commented on May 12, 2015

    @jsha
    Member

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

  2. reedy commented on May 12, 2015

    @reedy
    ContributorAuthor

    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?

  3. jsha commented on May 12, 2015

    @jsha
    Member

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

  4. zmanian commented on May 12, 2015

    @zmanian

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

  5. reedy commented on May 12, 2015

    @reedy
    ContributorAuthor

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

  6. reedy commented on May 12, 2015

    @reedy
    ContributorAuthor

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

  7. Mikaela commented on Sep 3, 2015

    @Mikaela
    Contributor

    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?

  8. gloomy-ghost commented on Nov 6, 2017

    @gloomy-ghost
    Collaborator

    Now we use the same codebase for Chrome and Firefox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions