themesberg / themesberg/flowbite
Class conflicting issue for speed dial (Using angular)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 862
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Class conflicting issue for speed dial (Using angular)
Sometimes the speed dial doesn't work. Sometimes it works, but while it works the page becomes stuck (not smooth scrolling)
Also, there is a class conflict issue. It's showing a warning
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Speed dial to work smoothly
Screenshots
https://storage.googleapis.com/msgsndr/RKjSVFlud4tomMYa0uQc/media/64fc2f77c42c81c327a5c3e2.jpeg
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the speed dial behavior in the Angular integration and inspect the reported class-conflict warning. The issue provides no reproduction steps or file names; done means the speed dial works smoothly without the warning or scrolling problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, tailwindcss
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100