XF 2.3 Blurry buttons on OSX

Ferdinand

Well-known member
I am so frustrated with the response about something that should have been caught in beta testing before we got to this version as I use safari and I upgraded because I have been with XF for nearly a decade and I'm sure there is a simple extra.less fix someone more experienced than me could write.

Anywho, long story short I have to ask the community for help because XF are unwilling to give me a quick patch for our buttons.

Does anyone know how to stop the blurry post button text in XF 2.3.4?
 

Attachments

  • Screenshot 2024-11-20 at 14.05.12.webp
    Screenshot 2024-11-20 at 14.05.12.webp
    41.1 KB · Views: 31
Solution
Yes it is fixable and it will be available in the next release.

It isn't a trivial change so we're not providing a patch at this time. Bug fix releases are typically 4-8 weeks at the moment, though I'd estimate closer to 8 (so probably some time in December).

Hopefully you can at least now appreciate that this isn't a global issue affecting everyone. It seems to be very much dependent on the version of Safari and potentially the display hardware as in your case.

Here's the bug thread for reference:

Nothing custom, just whatever the browser or site styling is. Not seen anyone else have this so it's likely something configured on your end.
It's the display, for some reason on this monitor the problem occurs. It is fixable as the new XF community here is okay>
 

Attachments

  • Screenshot 2024-11-20 at 16.13.36.webp
    Screenshot 2024-11-20 at 16.13.36.webp
    15.4 KB · Views: 14
Yes it is fixable and it will be available in the next release.

It isn't a trivial change so we're not providing a patch at this time. Bug fix releases are typically 4-8 weeks at the moment, though I'd estimate closer to 8 (so probably some time in December).

Hopefully you can at least now appreciate that this isn't a global issue affecting everyone. It seems to be very much dependent on the version of Safari and potentially the display hardware as in your case.

Here's the bug thread for reference:

 
Solution
Back
Top Bottom