Update :in-range/:out-of-range when steppable min/max/value changes.

Update :in-range/:out-of-range when steppable min/max/value changes.

We called pseudoStateChanged in a lot of cases where it wasn't
necessary. It should suffice to call it for the mentioned pseudo
classes when the min and max attributes changes, or the value is
changed, either as an attribute or as a result of user input.

This should fix the performance regressions in issue 704775.

R=tkent@chromium.org
BUG=704775
Review-Url: https://codereview.chromium.org/2774723004
Cr-Commit-Position: refs/heads/master@{#459733}
Committed: https://chromium.googlesource.com/chromium/src/+/b2cdcbfc13078c618e722c988e5afc0a5d435e74

[rune, 2017-03-24 14:50:25]

The CQ bit was checked by rune@opera.com to run a CQ dry run

[commit-bot: I haz the power, 2017-03-24 14:50:47]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[rune, 2017-03-24 14:52:50]

ptal

I was unsure whether the inRangeChanged() code should be on the
HTMLInputElement, the InputView, or the InputType.

[commit-bot: I haz the power, 2017-03-24 15:56:09]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-24 15:56:10]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[tkent, 2017-03-26 23:38:19]

> I was unsure whether the inRangeChanged() code should be on the
HTMLInputElement, the InputView, or the InputType.

I think it should be on InputType class.  Anyway, this CL lgtm.

[rune, 2017-03-27 07:56:03]

On 2017/03/26 23:38:19, tkent wrote:
> > I was unsure whether the inRangeChanged() code should be on the
> HTMLInputElement, the InputView, or the InputType.
> 
> I think it should be on InputType class.  Anyway, this CL lgtm.

Moved to InputType.

[rune, 2017-03-27 07:56:08]

The CQ bit was checked by rune@opera.com

[rune, 2017-03-27 07:56:08]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org
Link to the patchset: https://codereview.chromium.org/2774723004/#ps20001
(title: "Moved code to InputType class.")

[commit-bot: I haz the power, 2017-03-27 07:56:24]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-27 09:37:57]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1490601368406260,
"parent_rev": "8e45386fb683e55cd2354e5537c352b3cf8303c6", "commit_rev":
"b2cdcbfc13078c618e722c988e5afc0a5d435e74"}

[commit-bot: I haz the power, 2017-03-27 09:38:45]

Description was changed from

==========
Update :in-range/:out-of-range when steppable min/max/value changes.

We called pseudoStateChanged in a lot of cases where it wasn't
necessary. It should suffice to call it for the mentioned pseudo
classes when the min and max attributes changes, or the value is
changed, either as an attribute or as a result of user input.

This should fix the performance regressions in issue 704775.

R=tkent@chromium.org
BUG=704775
==========

to

==========
Update :in-range/:out-of-range when steppable min/max/value changes.

We called pseudoStateChanged in a lot of cases where it wasn't
necessary. It should suffice to call it for the mentioned pseudo
classes when the min and max attributes changes, or the value is
changed, either as an attribute or as a result of user input.

This should fix the performance regressions in issue 704775.

R=tkent@chromium.org
BUG=704775

Review-Url: https://codereview.chromium.org/2774723004
Cr-Commit-Position: refs/heads/master@{#459733}
Committed:
https://chromium.googlesource.com/chromium/src/+/b2cdcbfc13078c618e722c988e5a...
==========

[commit-bot: I haz the power, 2017-03-27 09:38:46]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/b2cdcbfc13078c618e722c988e5a...