I am Not really a fan of how Daisyui 5 looks compared to Daisyui 4

[Keshav-writes-code]

Is it just me?
Daisyui 4 felt Soft and Roundy
Daisyui 5 feels not that Soft with its interractions and looks

Also, Look at how the text looks in the Docs Sidebar in both version

Daisyui v4

Daisyui v5

The text has gone brighter for sure but it seems a little blurry to my eye
the old text feels more clearer and light on the eye

[saadeghi]

The contrast for text color is increased in the default dark theme. Nothing more. Font is same, font size is same.

v4:

v5:

Suggestion:

• Go to https://daisyui.com/theme-generator/
• Pick dark theme
• Choose a darker text color

These are the exact v4 colors for dark theme if you need:
https://github.com/daisyui/v4-themes-for-v5/blob/master/dark.css

[Keshav-writes-code]

thanks!!

[G-MontaG]

I’m new to the daisyUI community (first time reading the docs today), but I immediately noticed something that feels off in the Drawer sidebar.

The text in the sidebar appears blurry during/after the transition. This is easy to reproduce directly on the official site (daisyui.com), so no custom setup is needed.

It seems more like a rendering issue caused by CSS animations/transitions.

After inspecting the styles, I found that disabling:

will-change: transform;

makes the text render clearly again.

Here is small demo video: https://drive.google.com/file/d/17c_dBRIIty-xW1GQ4y6ubuRmpXomDlkn/view?usp=sharing

It’s subtle and a bit hard to capture on video, but it’s most noticeable on tightly spaced text like “Utilities & variables”, where the letters appear slightly smeared (letter t).

Mac, Chrome 146.0.7680.81

[saadeghi]

I'm watching your video with 0.25x speed and I couldn't see the render issue you mentioned.
I couldn't see such issue on my Mac/Chrome either 🤔

[G-MontaG]

I agree the blur is very subtle, but once you notice it, it’s hard to unsee. It may also be hardware-dependent (GPU, screen resolution, scaling, etc.), so not everyone will experience it the same way.

I don’t think this is strictly a code issue, but more related to how browsers render transform with will-change.

For anyone who unlucky like me, a simple workaround is to override the CSS to will-change: unset; on aside tag.