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

Change preferences page into appearance, notifications, and other #10977

Merged
merged 1 commit into from
Jun 7, 2019

Conversation

Gargron
Copy link
Member

@Gargron Gargron commented Jun 6, 2019

Notification and appearance preferences now inherit all methods from the preferences controller, merely overriding the redirect-after-save path.

Appearance preferences:

image

Other preferences:

image

@Gargron Gargron added ui Front-end, design work in progress Not to be merged, currently being worked on labels Jun 6, 2019
@Gargron Gargron force-pushed the fix-appearance-preferences branch from f9365aa to 2011641 Compare June 6, 2019 11:28
@Gargron Gargron removed the work in progress Not to be merged, currently being worked on label Jun 6, 2019
@Gargron Gargron marked this pull request as ready for review June 6, 2019 11:34
@ClearlyClaire
Copy link
Contributor

The “recommended” stuff seems weird. If that's recommended, shouldn't that be the default? (In the case of gif autoplay I know why this isn't the default, and I guess I understand why you would want to nudge people to enable it, though). Also it's unclear why it's recommended. Especially stuff that does the user no good (e.g., disclosing the authoring app)

I'm not sure CW stuff and confirmation modals really fall into “appearance” (not sure about language either tbh)

@Gargron
Copy link
Member Author

Gargron commented Jun 6, 2019

Also it's unclear why it's recommended. Especially stuff that does the user no good (e.g., disclosing the authoring app)

This is worded a bit unfairly. In the vast majority of cases disclosing the app used to make a post has no harmful effect on anyone, and it's good for the ecosystem by promoting good apps. That is why it is on by default. In fact, all the "recommended" items are the ones that are on by default, except GIF autoplay, which is off by default for accessibility reasons but is a good option if you don't suffer from motion sickness. In the case of "group boosts" for example, the option is a bit arcane. Who will know what it really means? So I think it's good to put a "recommended" label on that, as if to signal: This is on by default for a good reason. Leave it there.

I'm not sure CW stuff and confirmation modals really fall into “appearance” (not sure about language either tbh)

I don't feel any doubt on this part.

@Gargron Gargron force-pushed the fix-appearance-preferences branch from 2011641 to 266495a Compare June 6, 2019 18:19
@Gargron Gargron requested a review from ykzts June 7, 2019 01:26
@Gargron Gargron merged commit 1db4117 into master Jun 7, 2019
@Gargron Gargron deleted the fix-appearance-preferences branch June 7, 2019 01:58
@trwnh
Copy link
Member

trwnh commented Jun 7, 2019

i still think "hide your network" and "opt out of search engine indexing" belong with the other "profile" settings. also, grouping boosts in timelines sounds like an appearance thing

edit: ah whoops didn't realize this already got merged while i was writing the comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ui Front-end, design
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants