Closed Bug 1180670 Opened 9 years ago Closed 3 months ago

Synthethic click activation (ie. HTMLElement.click()) should not find the nearest activatable element

Categories

(Core :: DOM: Core & HTML, defect)

defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: jdm, Unassigned)

References

()

Details

(Whiteboard: [domcore-bugbash-triaged])

According to https://www.w3.org/Bugs/Public/show_bug.cgi?id=27430 the call to click() in the testcase should only operate on the given element, which is not activatable (lacking an href attribute). The authentic activation steps explicitly say to find the nearest activatable element, but synthetic activation should not.
Flags: needinfo?(bugs)
I will note that only IE follows the spec right now; Gecko, Blink, and Webkit disagree.
The spec has mostly do-something-else-than-what-most-of-the-browser-engines-have-done-forever model
for default handling activation, so I'd be very careful when changing anything to follow the spec here.
I'm quite sure we'd get regression bugs if we changed the behavior.
Flags: needinfo?(bugs)
Component: DOM → DOM: Core & HTML
Severity: normal → S3

The spec has changed around this topic several times and so has implementation, so I think we should just close this one. Please open a new bug if needed.

Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → INACTIVE
Whiteboard: [domcore-bugbash-triaged]
You need to log in before you can comment on or make changes to this bug.