Open Issues Need Help
View All on GitHubOfficial React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS
AI Summary: Users of `flowbite-react` version 0.6.4 are reporting that `Button` components rendered as `<a>` tags (using `as="a"`) lack a hover state, unlike standard `Button` elements. This results in inconsistent visual feedback, as both types are expected to display a hover effect. The issue might stem from a recent PR.
Official React components built for Flowbite and Tailwind CSS
Official React components built for Flowbite and Tailwind CSS