🐛 `ProgressBar` and `ProgressBar` are slightly different from their native counterparts
Open
bug
enhancement
- Dominant language
- Dart
- Stars
- 3.5k
- Forks
- 506
- Avg merge
- 11d 2h
- Merged PRs (30d)
- 3
Description
Both consume a lot of CPU energy just by existing.
When looking at their native counterparts, they have a design differences.
Progress bar lacks paused and error states:
```
ProgressBar.paused()
ProgressBar.error()
```
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the ProgressBar entry point and compare its behavior with the native counterparts; verify the reported CPU usage and determine how paused and error states should be represented. Done means the component supports both states and its idle resource use is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100