New issue
Advanced search Search tips

Issue 696686 link

Starred by 3 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task

Blocked on:
issue 713711

Blocking:
issue 693521



Sign in to add a comment

Fire mouse events for disabled form controls

Project Member Reported by dtapu...@chromium.org, Feb 27 2017

Issue description

Similar to  issue 695979  we should fire mouse events (other than click) for disabled form controls.
 
Cc: mustaq@chromium.org rbyers@chromium.org nzolghadr@chromium.org
Blocking: 693521
Labels: -Type-Bug Type-Launch-OWP
Blockedon: 713711
Project Member

Comment 5 by bugdroid1@chromium.org, Apr 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/af6f27363128a72a89cb581f3073c0e068854308

commit af6f27363128a72a89cb581f3073c0e068854308
Author: dtapuska <dtapuska@chromium.org>
Date: Mon Apr 24 21:49:14 2017

Send mouse events for disabled form controls.

Intent to Implement:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/rhNbsYDBJes/Jvmtv6IbBwAJ

The HTML spec clearly indicates that only click should be prevented. Add
a flag to change the behaviour and put it as an experimental flag for now.

Click events will not be dispatched if a disabled form control exists in
the event path.

BUG=696686, 693521

Review-Url: https://codereview.chromium.org/2832073003
Cr-Commit-Position: refs/heads/master@{#466783}

[add] https://crrev.com/af6f27363128a72a89cb581f3073c0e068854308/third_party/WebKit/LayoutTests/fast/forms/mouseevent_disabled_form_control.html
[modify] https://crrev.com/af6f27363128a72a89cb581f3073c0e068854308/third_party/WebKit/Source/core/dom/Node.cpp
[modify] https://crrev.com/af6f27363128a72a89cb581f3073c0e068854308/third_party/WebKit/Source/core/events/EventPath.cpp
[modify] https://crrev.com/af6f27363128a72a89cb581f3073c0e068854308/third_party/WebKit/Source/core/events/EventPath.h
[modify] https://crrev.com/af6f27363128a72a89cb581f3073c0e068854308/third_party/WebKit/Source/core/events/MouseEvent.cpp
[modify] https://crrev.com/af6f27363128a72a89cb581f3073c0e068854308/third_party/WebKit/Source/core/html/HTMLSelectElement.cpp
[modify] https://crrev.com/af6f27363128a72a89cb581f3073c0e068854308/third_party/WebKit/Source/platform/RuntimeEnabledFeatures.json5

Comment 6 by owe...@chromium.org, Sep 12 2017

Labels: migrated-launch-owp Type-Task
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge
Status: Started (was: Assigned)
Intent to Ship here: https://groups.google.com/a/chromium.org/d/msg/blink-dev/KHXNJINUrj0/OAAh-sWuAwAJ
Owner: nzolghadr@chromium.org

Sign in to add a comment