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

Rageshake submission dialog should default screenshots to off #6261

Closed
kittykat opened this issue Jun 8, 2022 · 1 comment · Fixed by #6297
Closed

Rageshake submission dialog should default screenshots to off #6261

kittykat opened this issue Jun 8, 2022 · 1 comment · Fixed by #6297
Assignees
Labels
A-Rageshake O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@kittykat
Copy link
Contributor

kittykat commented Jun 8, 2022

Your use case

What would you like to do?

Not send screenshots with a rageshake by default

Why would you like to do it?

Because it's too easy to miss that a screenshot is being attached, so too easy to send one by default and at least in my case the screenshots are rarely relevant to the rageshake or often contain private data

How would you like to achieve it?

By defaulting the screenshot option to off

Have you considered any alternatives?

No response

Additional context

No response

Are you willing to provide a PR?

No

@kittykat kittykat added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Jun 8, 2022
@ouchadam ouchadam self-assigned this Jun 13, 2022
@kittykat kittykat added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Jun 14, 2022
@ouchadam
Copy link
Contributor

Fixed in 1.4.24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rageshake O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants