Progressbar: broken in IE11 with value always = 1

[maxokorokov]

Always generates progressbars with value=1

Screenshot from the demo:

Generated html:

<progress value="1" max="100" ng-reflect-value="50" ng-reflect-max="100"> ... </progress>

From (MDN):

• if the max is not set value should be between 0 and 1
• if the max is set value should be between 0 and max

So looks like this template causes the issue (from progressbar.ts):

<progress [value]="getValue()" [max]="max" ... >

Because this seem to work:

<progress [max]="max" [value]="getValue()"  ... >

Apparently after setting value to, say 50, IE limits it to 1, because max is not yet there.

Not sure if it's the best solution though

[pkozlowski-opensource]

Are you saying that order of attributes matter???

[maxokorokov]

@pkozlowski-opensource yep, it this case yes... so that's why I'm not sure what to do with this information yet :)

[pkozlowski-opensource]

Sight... IE... So it seems like it has some internal state and fails to update it properly.... If swapping order makes IE happy and doesn't hurt other browsers, let's make this change. I'm not sure we've got other way of controlling order of bindings...