Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current Version #1227

Closed
topnotchaero opened this issue Oct 25, 2019 · 6 comments
Closed

Current Version #1227

topnotchaero opened this issue Oct 25, 2019 · 6 comments

Comments

@topnotchaero
Copy link

Will legacy add-ons work with the current version?

@hawkeye116477
Copy link
Contributor

hawkeye116477 commented Oct 25, 2019

They will work if someone modify it.
https://github.com/MrAlex94/Waterfox/wiki

@Telmesomething
Copy link

Will legacy add-ons work with the current version?

Well, if you think about it there wouldn't be any point in maintaining the Classic version if the new flavor supported legacy extensions.

@grahamperrin
Copy link

This issue is for Waterfox Current, not for Waterfox Classic.

@Telmesomething please raise a separate issue. Thanks

@grahamperrin
Copy link

PS, maybe some misunderstanding around the new approach to versioning.

2019.10 = two quite different flavours of Waterfox (if we think of Classic and Current as flavours).

The first screenshot at https://new.reddit.com/r/waterfox/comments/dmtmpq/-/ might help to tell the difference.

@Telmesomething
Copy link

Sorry Graham, I have to apologize. I downloaded Classic instead of Current simply because I didn't scroll further down the releases page. I've now installed the correct one and it works just fine.

Maybe it might be a good idea to reverse the layout so that Current appears at the top?

@grahamperrin
Copy link

Thanks,

layout

#582 (comment) – I'll quote you and reply there.

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

No branches or pull requests

5 participants