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.

Keep opera browser plugin up to date #19679

Closed

Description

@Root-Core

Type: other

Please provide the current version for Opera users.
It would also be awesome, if the Opera plugin was released as frequently as for other browsers.

Last update: 08 January 2019 - which is way too old

I'm using the Chrome Plugin - but if this is the solution, please remove the plugin altogether from Opera addon store.

Activity

  1. zoracon commented on Oct 14, 2020

    @zoracon
    Contributor

    Sorry for the lag on updating in Opera. For what's it's worth, there is no security update, if there was we wouldn't have allowed the older version to remain as in Opera.

    The problem is that many downstream channels and officially supported channels rely on a major file (rulesets.default) that Opera wants us to rename for their standards (standards Chrome does not have). Changing the name would be easy enough if it didn't require so much coordination because many downstream channels rely on it.

    But you are right, this delay on updating is not a solution. I will weigh the pros and cons of continued support in Opera (the team won't budge on their MIME type blocker, I asked) and make a decision this week.

    Thank you!

  2. Root-Core commented on Oct 15, 2020

    @Root-Core
    Author

    Without knowing any details, would aliasing the rulesets.default file be a solution or rename it for the opera release while building it?

  3. pipboy96 commented on Oct 15, 2020

    @pipboy96
    Contributor

    @Root-Core The main problem would be the fact we would have to publish a separate .crx for Opera.

  4. Root-Core commented on Oct 15, 2020

    @Root-Core
    Author

    Why not releasing the crx for other browsers too? Does it lead to any problems, if the file has another name in the release?
    I imagine that the downstreams etc. rely only on the source beeing named as is, not on the name in the packed version.

    Just an idea, but as I stated.. i have no idea about the structure of this project, so i'm sorry if that is stupid.

  5. zoracon commented on Oct 15, 2020

    @zoracon
    Contributor

    @Root-Core Not stupid at all, some downstream partners directly reference the naming convention. And as @pipboy96 said, we would need to release a separate CRX file for Opera. I am currently looking at the build script to see if the workflow checks out.

  6. zoracon commented on Nov 9, 2020

    @zoracon
    Contributor

    This is up to date in Opera now! Thank you.

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

Metadata

Metadata

Assignees

Labels

EFFSomeone at EFF needs to look intoopera

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions