New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Fixed
Closed: Feb 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Sign in to add a comment

Issue 695979: Fire pointer events for disabled form controls

Reported by, Feb 24 2017 Project Member

Issue description

It appears we followed the broken mouse model of not firing events for disabled form controls.

We really should be firing events regardless of state.

See issue:

Comment 1 by, Feb 24 2017

Components: Blink>Input
Labels: -Pri-3 Hotlist-Input-Dev Hotlist-Interop Pri-2
Status: Assigned (was: Untriaged)

Comment 2 by, Feb 24 2017

This looks trivial:

The isMouseEvent check just needs a '&& !isPointerEvent' clause.

So I agree we should just fix this.  But can we also track investigating / fixing the mouse event case too?  It may be easy to restrict this wart to 'click' events.

Comment 3 by, Feb 24 2017


Comment 4 by, Feb 24 2017

rbyers@ the code is actually here:

And PointerEvent.h has a virtual isMouseEvent() that returns false; so that piece of code is really nothing relevant.

I put up a change here: just need to write a layout test for it.

Comment 5 by, Feb 24 2017

Ah, thanks - guess I should stop pretending I know this code anymore ;-)

Comment 6 by, Feb 24 2017

hey I commented on the public bug that I didn't know where it was.. had to debug. The mouse code looks entirely confusing like people just littered isDisabledFormControl in various spots.

Comment 8 by, Feb 27 2017

Status: Fixed (was: Assigned)

Comment 9 by, Mar 8 2017

Labels: M-58

Sign in to add a comment