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

Ability to disable new options by default #2664

Closed
jhpratt opened this issue Jan 4, 2020 · 3 comments · Fixed by #2668
Closed

Ability to disable new options by default #2664

jhpratt opened this issue Jan 4, 2020 · 3 comments · Fixed by #2668
Labels
meta Related to Refined GitHub itself under discussion

Comments

@jhpratt
Copy link

jhpratt commented Jan 4, 2020

How hard would it be to have the ability to disable any new options by default? There have been a number of changes recently that I don't care for, and I find myself struggling to find the name of the preference that was added.

@fregante
Copy link
Member

fregante commented Jan 4, 2020

Like you can’t disable new features in any websites, we shouldn’t do it here either. We don’t actually guarantee that features don’t depend on each other and some CSS is injected anyway.

Also what’s “new”? Would an improved feature be considered new? What if infinite-scroll starts working on new pages?

Not worth the effort

@fregante fregante closed this as completed Jan 4, 2020
@jerone
Copy link
Contributor

jerone commented Jan 4, 2020

I like the way how Tab Session Manager highlights new settings:

image

Very easy to author if the new setting is relevant for me.

@fregante
Copy link
Member

fregante commented Jan 5, 2020

@jerone not a terrible idea, but then the extension needs to keep track of new features locally (I don't want to have to remember to un-mark a feature as new nor have to add a dateAdded date right before merging a PR)

PR welcome if the code to add that isn't too long :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Related to Refined GitHub itself under discussion
Development

Successfully merging a pull request may close this issue.

3 participants