Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×This is just one example. If you need more, let me know. Compare the word quality on the left and the right. It is jarring to see normal text, then every time I open a drop down on your site I have to see this texture-torture. Please fix it, I beg you. No more.
Hello @David Mitchell ,
Thanks for the feedback. And to get better understanding of what you are looking for, what recommendations would you have for the style changes?
Currently the referenced menu dropdown is configured per the Atlassian User iInterface Design Guidelines as:
.aui-dropdown2.aui-style-default a {
color: #333;
padding: 3px 10px;
text-decoration: none;
}
font-family: Arial,sans-serif;
font-weight: 400;
Regards,
Earl
I figured out why I was seeing the font blurry! It is because my zoom != 100%. Looks like my zoom in on the page at 110%. That is why all of the drop downs are blurry for me. Would you guys be able to implement the fix listed here?
Looks like the answer is in here: https://github.com/twbs/bootstrap/issues/23590
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @David Mitchell ,
Thanks for the clarification I could not tell from the screenshot that you meant that the text was blurry, I thought you were talking about the text formatting specifically.
But yes That is odd as it appears to only be affecting my system at a zoom level of 110% but additionally only on my external 1080P monitor, my main display is a retina display and the text is crisp and clear at the same zoom, but on the other monitor 110% is blurry and going to a higher or lower zoom level the menu text is rendering fine as well so 110% on a 1080p monitor seems to trigger this Bug.
This also looks to be similar to a previous bug that was closed out because the behavior was not reproducible at the time it was being reviewed, viewable at the link below and I suspect this was hard to track down due to varying hardware specs between the testers leading to the closure:
With these new details I created a New Bug to track the updated behavior, make sure to follow the Bug if you want updates on the status, and feel free to add any additional comments on behavior you notice related to this as it will help out in finding a fix.
The new Bug can be viewed here:
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.