fix(input): keep track of min/max attrs on-the-fly

[runk]

Now input[type=button] keeping track of both min and max attrs even if they change over time.

[mary-poppins]

Thanks for the PR!

• Contributor signed CLA now or in the past
  • If you just signed, leave a comment here with your real name
• PR's commit messages follow the commit message format

If you need to make changes to your pull request, you can update the commit with git commit --amend.
Then, update the pull request with git push -f.

Thanks again for your help!

[runk]

CLA / Real name is Dmitry Shirokov deadrunk@gmail.com

[IgorMinar]

LGTM

@matsko this is assigned to you. are you waiting for something before merging it? I'm not going to merge it now in case you are waiting for something...

[matsko]

@IgorMinar Yup. Merging it now. At the time I couldn't verify the CLA thing.

[matsko]

MERGED

[matsko]

Landed as 4b653ae

[quazzie]

This does not re-validate the value when changing min/max.
Does not test form-validity.

If i change min/max the control is still valid even if the value is out of range.

[quazzie]

And input[type=button] ?

[runk]

@quazzie could you show your code please? On the jsfiddle or somewhere else.

[quazzie]

http://plnkr.co/edit/cVOninI9I1451PHYJUWG?p=preview

[quazzie]

#4788

[runk]

@quazzie I figured out why this worked for me - I changed the model's value at the same time with the min's value. It triggers the $setViewValue method when you do so.

[runk]

@quazzie there is alternative solution #4797.

I have a feeling that this trick with $setViewValue methods looks like a hack.. @matsko any thoughts?

[quazzie]

@runk yeah that's maybe a nicer way to do it. But please add the tests.
The only thing i can complain about is that your solution uses 2 'watches'.

[runk]

Yeah, sure @quazzie. It looks like that tests work fine.