Re: [pointerevents] Clarify what event is `userEvent` to consider `click`/`auxclick` event target after `touchend` (or `pointerup`) (#508)

> I believe if you try chrome with the `--enable-blink-features=BoundaryEventDispatchTracksNodeRemoval` flag that it will dispatch to the captured target of the pointerevent instead (code [here](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/input/pointer_event_manager.cc;l=1091;bpv=1;bpt=1?q=pointereventmanager)). 

Well, I assume that it's enabled by default when I run WPT on Chrome from `./mach wpt` command in Firefox development environment (I use Chrome Canary). The command does not accept to explicitly enable it, but in the same condition, all tests of [pointerevent_after_target_removed.html?mouse](https://wpt.fyi/results/pointerevents/pointerevent_after_target_removed.html%3Fmouse?label=experimental&label=master&aligned&view=interop&q=label%3Ainterop-2023-events) pass so I believe that the feature is enabled by default when I run Chrome Canary from the command. However, my test unexpectedly pass on Chrome Canary.

When I run Chrome Canary, I see the following warning in the terminal:
```
 0:14.97 pid:56536 [4464:22700:0623/115359.500:WARNING:chrome_browser_main_win.cc(712)] Command line too long for RegisterApplicationRestart:  --allow-pre-commit-input --autoplay-policy=no-user-gesture-required --disable-background-networking --disable-backgrounding-occluded-windows --disable-client-side-phishing-detection --disable-default-apps --disable-hang-monitor --disable-infobars --disable-popup-blocking --disable-prompt-on-repost --disable-sync --enable-blink-features=DisableAhemAntialias --enable-experimental-web-platform-features --enable-features=FedCmWithoutWellKnownEnforcement,SecurePaymentConfirmationBrowser,GenericSensorExtraClasses --enable-logging=stderr --headless=new --host-resolver-rules="MAP nonexistent.*.test ^NOTFOUND, MAP *.test 127.0.0.1, MAP *.test. 127.0.0.1" --ignore-certificate-errors-spki-list=sCJ8962Wxqgz44IKoPQLcDT7YRRAxO2w1iYIqpMYHhg=,0Rt4mT6SJXojEMHTnKnlJ/hBKMBcI4kteBlhR1eTTdk= --ip-address-space-overrides=127.0.0.1:8002=private,127.0.0.1:8003=public,127.0.0.1:8445=private,127.0.0.1:8446=public --log-level=0 --no-first-run --no-service-autorun --noerrdialogs --password-store=basic --remote-debugging-port=0 --short-reporting-delay --test-type=webdriver --use-fake-device-for-media-stream --use-fake-ui-for-digital-identity --use-fake-ui-for-fedcm --use-fake-ui-for-media-stream --use-mock-keychain --user-data-dir="C:\Temp\scoped_dir56536_1771468703" --webtransport-developer-mode --restore-last-session --restart
```

Doesn't `--enable-experimental-web-platform-features` enable the feature as well?

-- 
GitHub Notification of comment by masayuki-nakano
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/508#issuecomment-2184405409 using your GitHub account


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

Received on Sunday, 23 June 2024 02:57:24 UTC