"Updating" spinner is blurry
See original GitHub issueDescription
“Updating” spinner is blurry
Version
- GitHub Desktop: 1.2.2
-
Operating system: macOS 10.13.4
-
Computer: MacBook Pro (Retina, 13-inch, Early 2013)
-
Monitor: Apple Cinema HD Display (1920 x 1200)
Steps to Reproduce
About > Check for Updates
Expected Behavior
Spinner should be sharp
Actual Behavior
Spinner is very blurry
(I have not checked Retina mode)
Additional Information

Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Image inside custom Spinner is blurry - android - Stack Overflow
When I separate every image correctly with the specific size in the corresponding folder, the problem was solved, and the image appeared ...
Read more >Spinner vs Blur for image loading in 2017? - UX Stack Exchange
Progressively loading images (blurry -> crisp) does that, however, they don't indicate when the image is fully loaded. For example, if the final ......
Read more >Spinner - Android Developers
The items in the Spinner come from the Adapter associated with this view. ... a net loss in performance due to the cost...
Read more >Your Loading Spinner Is a UX Killer! Here's an Alternative
A determinate loading animation indicates how much longer a user has to wait with hints like percentage complete, minutes left or a bar...
Read more >Stop Using A Loading Spinner, There's Something Better
Stop using those boring loading spinners in your user interfaces. Seriously. ... by Suleiman · Published February 28, 2017 · Updated October 2,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@gingerbeardman thank you for the detailed issue and the help in putting together a reduced test case. However, please let’s refrain from the value judgements such as “lazy” and “unprofessional”. Focusing on constructive criticism is the best way to make your case for getting something fixed.
Since this isn’t something that we have a solution for and it’s a minor cosmetic issue, I’m going to close it for now. However, the invitation remains if someone knows if there’s a low effort way to tackle this, feel free to respond in this issue and we can evaluate whether to reopen. Thanks!