Bug 146637 - Synthethic click activation (ie. HTMLElement.click()) should not find the nearest activatable element
Summary: Synthethic click activation (ie. HTMLElement.click()) should not find the nea...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-06 06:12 PDT by Josh Matthews
Modified: 2015-07-11 06:08 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Matthews 2015-07-06 06:12:09 PDT 
http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=3556

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 target element, which in the testcase is not activatable (an anchor lacking an href attribute). The authentic activation steps explicitly say to find the nearest activatable element, but synthetic activation (ie. HTMLElement.click()) should not.