You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
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.
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.
@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.
Activity
zoracon commentedon Oct 14, 2020
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!
Root-Core commentedon Oct 15, 2020
Without knowing any details, would aliasing the
rulesets.defaultfile be a solution or rename it for the opera release while building it?pipboy96 commentedon Oct 15, 2020
@Root-Core The main problem would be the fact we would have to publish a separate .crx for Opera.
Root-Core commentedon Oct 15, 2020
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.
zoracon commentedon Oct 15, 2020
@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.
zoracon commentedon Nov 9, 2020
This is up to date in Opera now! Thank you.