Test List
Rationale
While I'm investigating the behavior change, I found 3 issues.
One is filed as w3c/pointerevents#507. The dblclick event target may be different from click, but is it expected by developers?
The others are filed as w3c/pointerevents#508. The click event target may be different if user inputs from a mouse or touch device. Additionally, current defined behavior is conflict with an old bug fix of Mozilla for web-compat issue in bxSlider (I don't reproduce it with current defined behavior in their example, but the originally reported URL has gone. Therefore, I'm not 100% sure that changing the behavior would break bxSlider again in some cases).
@zcorpan, @smaug----, @mustaqahmed, @flackr
Test List
Rationale
While I'm investigating the behavior change, I found 3 issues.
One is filed as w3c/pointerevents#507. The
dblclickevent target may be different fromclick, but is it expected by developers?The others are filed as w3c/pointerevents#508. The
clickevent target may be different if user inputs from a mouse or touch device. Additionally, current defined behavior is conflict with an old bug fix of Mozilla for web-compat issue in bxSlider (I don't reproduce it with current defined behavior in their example, but the originally reported URL has gone. Therefore, I'm not 100% sure that changing the behavior would break bxSlider again in some cases).@zcorpan, @smaug----, @mustaqahmed, @flackr