Revert of Update of change event for input type number (https://codereview.chromium.org/128133002/)

Reason for revert:
INPUT element dispatches extra events.

Original issue's description:
> Do not dispatch 'change' events during pressing spin buttons for input[type=number].
>
> TextFieldInputType sends change event for its derived class. Change is
> done for DispatchInputAndChangeEvent to behave similar to
> DispatchChangeEvent.
> DispatchChangeEvent is generated by Range, Radio, File and Checkbox
> input type.
> DispatchInputAndChangeEvent is generated by inputtype for step up and
> down, BaseChooser/BaseMultipleFieldsDateandTime also generates
> DispatchInputAndChangeEvent.
> Since it is different set of inputs that generate DispatchChange and
> DispatchInputAndChange, both are kept but behavior is changed; this
> allows spin button to handle mouseup event.
> Keyboard events are also handled for spin button.
>
> R=tkent
> BUG=155747
> TEST=automated
>
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=165300

TBR=keishi@chromium.org,habib.virji@samsung.com
NOTREECHECKS=true
NOTRY=true
BUG=155747

Review URL: https://codereview.chromium.org/157813010

git-svn-id: svn://svn.chromium.org/blink/trunk@166983 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix race condition in focused element check

If the focused element becomes focusable again while the check focus timer is
running, we would erroneously clear its focus.

R=esprehn@chromium.org
BUG=342928

Review URL: https://codereview.chromium.org/153973006

git-svn-id: svn://svn.chromium.org/blink/trunk@166984 bbb929c8-8fbe-4397-9dbb-9b2b20218538