[pointerevents] Different click event order behavior between Firefox , ie , edge and Chrome/Safari (#634)

TurnerXi has just created a new issue for https://github.com/w3c/pointerevents:

== Different click event order behavior between Firefox , ie , edge and Chrome/Safari ==
Hi，I found the different trigger order  in different browser when I click the target element which bounded with useCapture=false first and then bounded with useCapture=true .

**Steps to reproduce**
```
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>Title</title>
    <style>
        #a {            width: 100%;            height: 300px;            background-color: lightblue;        }
    </style>
</head>
<body>
    <div id="a"></div>
</body>
<script>
    var a = document.getElementById("a");
    a.addEventListener('click', function() {  console.log('a');  },false);
    a.addEventListener('click', function() {  console.log('a1');  }, true);
</script>
</html>
```
**Results**
Chrome / Safari:
```
a1
a
```
Firefox / IE / Edge:
```
a
a1
```

according to the spec [https://w3c.github.io/uievents/#event-flow](https://w3c.github.io/uievents/#event-flow)

> The capture phase: The event object propagates through the target’s ancestors from the Window to the target’s parent. This phase is also known as the capturing phase.

> The target phase: The event object arrives at the event object’s event target. This phase is also known as the at-target phase. If the event type indicates that the event doesn’t bubble, then the event object will halt after completion of this phase.

> The bubble phase: The event object propagates through the target’s ancestors in reverse order, starting with the target’s parent and ending with the Window. This phase is also known as the bubbling phase.

When I click the target element , it should be at-target phrase and trigger by listener order, but Chrome / Safari doesn’t .
So, what`s going on ?


Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/634 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 12 January 2026 22:14:45 UTC