-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Remove fomantic progress module #19760
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
Conversation
Replace it with HTML `<progress>` element. The bar won't go green at 100% anymore but I think it's not something that fits stylistically anyways.
|
Will this make the progress green? |
|
It seems working. https://jsfiddle.net/k8rjmaqu/ (it's just a personal opinion to make 100% as green, in case some people like it, I am fine to either. not a blocker) |
Yes it would work for the case where max is 100 like it is for the milestone bar, but I think we could also opt to make the milestone bar always green, like GitHub does. |
* giteaofficial/main: Move org functions (go-gitea#19753) [doctor] pq: syntax error at or near "." quote user table name (go-gitea#19765) [doctor] update the help with fix capabilities (go-gitea#19762) Remove fomantic progress module (go-gitea#19760) Make Ctrl+Enter (quick submit) work for issue comment and wiki editor (go-gitea#19729) Enable packages by default again (as described by docs) (go-gitea#19746) Replace blue button and label classes with primary (go-gitea#19763) Fix org package owner permissions (go-gitea#19742)
Replace it with HTML `<progress>` element. The bar won't go green at 100% anymore but I think it's not something that fits stylistically anyways.

Replace it with HTML
<progress>element. The bar won't animate or go green at 100% anymore but I think it's not something that fits stylistically anyways.