Environment
Vuetify Version: 4.0.4
Vue Version: 3.5.31
OS: Windows 10 (current)
Steps to reproduce
- Render
- Observe the progress bar β the last (3rd) chunk segment appears unfilled despite model-value === max
- Resize the browser window a few times β the segment may momentarily correct itself, then break again at certain viewport widths
Expected Behavior
All 3 chunk segments are filled when model-value equals max (300/300 = 100%)
Actual Behavior
Only 2 of 3 chunk segments appear filled. The last segment remains empty despite model-value === max. The bug is viewport-size sensitive β resizing the browser window a few times may reveal or temporarily fix it, confirming it is a pixel/layout calculation race in the chunk boundary rendering rather than a data issue.
Reproduction Link
https://play.vuetifyjs.com/#...
Other comments
The bug is viewport-size sensitive. At some widths the last chunk renders correctly; at others it stays empty even though the data is correct (300/300 = 100%). Resizing the container triggers a repaint that occasionally fixes it temporarily, confirming this is a pixel/layout calculation race in the chunk boundary math rather than a data or binding issue.
Images

Environment
Vuetify Version: 4.0.4
Vue Version: 3.5.31
OS: Windows 10 (current)
Steps to reproduce
Expected Behavior
All 3 chunk segments are filled when model-value equals max (300/300 = 100%)
Actual Behavior
Only 2 of 3 chunk segments appear filled. The last segment remains empty despite model-value === max. The bug is viewport-size sensitive β resizing the browser window a few times may reveal or temporarily fix it, confirming it is a pixel/layout calculation race in the chunk boundary rendering rather than a data issue.
Reproduction Link
https://play.vuetifyjs.com/#...
Other comments
The bug is viewport-size sensitive. At some widths the last chunk renders correctly; at others it stays empty even though the data is correct (300/300 = 100%). Resizing the container triggers a repaint that occasionally fixes it temporarily, confirming this is a pixel/layout calculation race in the chunk boundary math rather than a data or binding issue.
Images