You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The indication of frozen OS-versions isn't clear enough for our users
Solution Brainstorm
Background
With this pull request: getsentry/relay#1945
we are now letting our users know when an OS-version might be frozen, meaning that it might be higher than reported. This happens when a user doesn't have client hints enabled, and is using one of the browsers that started freezing OS versions.
example event: a1dc754f8f2a483d9615c05381c45ec8
"client_os: Windows >=10"
Request
Make it even more clear to users what is happening, if ">=" is detected in the client_os tag, spawn a tooltip that explains why the OS-version can't be accurately shown.
... or any other way that makes more sense to you
The text was updated successfully, but these errors were encountered:
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
Problem Statement
The indication of frozen OS-versions isn't clear enough for our users
Solution Brainstorm
Background
With this pull request: getsentry/relay#1945
we are now letting our users know when an OS-version might be frozen, meaning that it might be higher than reported. This happens when a user doesn't have client hints enabled, and is using one of the browsers that started freezing OS versions.
example event: a1dc754f8f2a483d9615c05381c45ec8
"client_os: Windows >=10"
Request
Make it even more clear to users what is happening, if ">=" is detected in the client_os tag, spawn a tooltip that explains why the OS-version can't be accurately shown.
... or any other way that makes more sense to you
The text was updated successfully, but these errors were encountered: