Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ProgressBar): new component #696

Closed

Conversation

Levy-from-Odessa
Copy link
Contributor

closes part of the #691

"An easy-to-animate progress bar, like the one from daisyUI."

@vercel
Copy link

vercel bot commented Sep 18, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
ui ✅ Ready (Inspect) Visit Preview Sep 18, 2023 5:16pm

@Levy-from-Odessa Levy-from-Odessa changed the title feat: add new element - ProgressBar feat(ProgressBar): new component Sep 18, 2023
@DarkGhostHunter
Copy link
Contributor

DarkGhostHunter commented Sep 19, 2023

I was literally fighting with the <progress> component, but it's too buggy to give it a worth shot in 2023. It's plain better to use <div> and mimic the <progress> behavior. There is a limit to what [$::-webkit-shenanigans]:something can handle.

Even from that, I think we should use <progress> instead of a div, mainly because the browser may pick it up for relevant actions, like it happens <time>.

Got it. You have to use an intermediate class (text-{color}-500) and then use bg-current on pseudo elements, to end up like [$::-webkit-shenanigans]:bg-current.

@benjamincanac
Copy link
Member

@Levy-from-Odessa Can we close this in favor of #697?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants