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

Remove chat menu item and toggle app switching privacy on by default #9636

Closed
rachelhamlin opened this issue Dec 10, 2019 · 1 comment · Fixed by #9638
Closed

Remove chat menu item and toggle app switching privacy on by default #9636

rachelhamlin opened this issue Dec 10, 2019 · 1 comment · Fixed by #9638

Comments

@rachelhamlin
Copy link
Contributor

rachelhamlin commented Dec 10, 2019

Problem

Combination issue spanning two product areas:

  1. Chat + menu—remove an option
  2. Profile > Privacy and security—turn a setting ON by default, alter copy

Implementation

  • Remove the Scan a QR code option from the chat menu

image

  • Change the copy of Hide content when switching apps to White out Status when switching apps
  • Set this toggle to be ON by defautl
    image

Acceptance Criteria

  • No more scan QR code option in chat menu
  • New copy for Privacy and security option
  • White out setting is on by default
@churik
Copy link
Member

churik commented Dec 13, 2019

Reason why scannig QR code option in chat menu should be removed:
from @hesterbruikman: it's out of context in chat. I genuinely love the scan anything feature, but in our current tab based UI we don't really have a fitting spot for such a global feature and it leads to an overwhelming nr of options inside chat. Would love to see it make a come back when we move to something like window-based navigation

flexsurfer added a commit that referenced this issue Dec 13, 2019
…default

Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
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

Successfully merging a pull request may close this issue.

3 participants