Skip to content

How to deal with the differences of Chrome & Firefox? #39

@flosse

Description

@flosse

How do we want to deal with the differences in the APIs of the various browsers?

For example in Firefox the tab field discarded is optional but in chrome it is mandatory.
Even more problematic is that e.g. the tab field hidden is not present in chrome at all but in Firefox.
Also MV3 is required for Chrome extensions but Firefox does not support MV3 yet.

Some possible approaches:

  • use feature flags
  • only implement APIs that are identical across browsers
  • make conflicting fields optional and/or do runtime checks and return corresponding errors
  • ignore Firefox

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions