<p dir="auto">For per-1.0 version, linear progress component has a consistent API with circle progress component, where the range of the progress can be set with 'max' and 'min' props. These APIs have been removed in 1.0, but it wasn't explicitly stated, and it was only implied in the examples that the value props linear progress now takes should be between 0 and 100. This causes a little confusing and unnecessary digging for those who migrated from pre 1.0 or new users who try to use both progress components.</p>


<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/callemall/material-ui/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>

<p dir="auto">Linear Progress and Circle Progress to have a consistent API implementation (with or without 'max/min' props')</p>
<h2 dir="auto">Current Behavior</h2>

<p dir="auto">Linear Progress only takes value prop, while Circle Progress accepts max/min.</p>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>

<p dir="auto">Use a simple component like this one below.</p>
<p dir="auto"><code class="notranslate">            &lt;LinearProgress mode='determinate' max={totalSeconds} min={0} value={totalSeconds - timePassed} /&gt;</code></p>
<p dir="auto">If I start with a total seconds &gt; 100, I would not see the linear progress bar moving until the last two minutes.</p>
<h2 dir="auto">Context</h2>
    
<p dir="auto">I am trying to give user different views that use different progress bars.</p>
<h2 dir="auto">Your Environment</h2>

<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>Material-UI</td>
<td>1.0.0-beta.18</td>
</tr>
<tr>
<td>React</td>
<td>16</td>
</tr>
<tr>
<td>browser</td>
<td></td>
</tr>
<tr>
<td>etc</td>
<td></td>
</tr>
</tbody>
</table>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/callemall/material-ui/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>

<p dir="auto">LinearProgress and CircularProgress should accept min, max and value props.<br>
When mode is 'determinate', the progress is calculated based on value between a scale of min to max.<br>
If min and max are not supplied, they default to 0 and 100 respectively (original behavior).<br>
<code class="notranslate">inlineStyles.primary.transform = 'scaleX(' + ((value - min) / (max - min)) + ')';</code></p>
<h2 dir="auto">Current Behavior</h2>

<p dir="auto">LinearProgress and CircularProgress accepts value prop.<br>
When mode is 'determinate', the progress is calculated based on value between a scale of 0 to 100.<br>
<code class="notranslate">inlineStyles.primary.transform = 'scaleX(' + value / 100 + ')';</code></p>
<h2 dir="auto">Context</h2>
    
<p dir="auto">This would simplify components that utilize LinearProgress and CircularProgress as parent components would no longer be responsible for scaling values between 0 and 100. I find it's pretty rare to have data already suitable for the progress components because it's not normally between 0 and 100.</p>
<h2 dir="auto">Your Environment</h2>

<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>Material-UI</td>
<td>1.0.0-beta.18</td>
</tr>
<tr>
<td>React</td>
<td>16.0.0</td>
</tr>
</tbody>
</table>