# Turbo progress bar .setValue accuracy

**URL:** <https://discuss.hotwired.dev/t/turbo-progress-bar-setvalue-accuracy/6334>\
**Category:** General\
**Created:** [May 28, 2025, 6:12am UTC](https://discuss.hotwired.dev/t/turbo-progress-bar-setvalue-accuracy/6334 "2025-05-28T06:12:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethancrawford](https://yyz1.discourse-cdn.com/flex027/user_avatar/discuss.hotwired.dev/ethancrawford/32/4111_2.png) [@ethancrawford](https://discuss.hotwired.dev/u/ethancrawford)\
**Post date:** [May 28, 2025, 6:12am UTC](https://discuss.hotwired.dev/t/turbo-progress-bar-setvalue-accuracy/6334/1 "2025-05-28T06:12:10Z")

</div>

I was recently a little surprised to notice that the progress bar’s .setValue function doesn’t just set the value to what’s passed in, and also sets the width of the bar less accurately the smaller the value is.  
No doubt there is a deliberate reason for this - if possible, would someone in the know be able to help me understand why it’s designed this way? 🤞