<ul><li>Developers working with ShadCN v4 and Tailwind CSS v4 noticed that buttons no longer showed the pointer cursor on hover, which broke user expectations.</li><li>A Github issue was opened to address this change, but it is actually a deliberate design choice where buttons now use the default cursor by design.</li><li>A custom CSS workaround has been shared by developers to restore the expected behavior and avoid pointer cursors on disabled buttons.</li><li>Originally, GUI buttons relied on visual affordances instead of cursors for interactivity, but web apps have different expectations with users now expecting visual cues like cursor changes for all clickable elements.</li></ul>

Why Are Buttons Losing the Pointer Cursor? The ShadCN and Tailwind Debate

Discover more