Re: [whatwg/dom] Proposal: Enable Custom Form Controls to (Optionally) Conceal Internal/Irrelevant Events (Issue #1368)

jakearchibald left a comment (whatwg/dom#1368)

I think having `input` and `change` be composed was a mistake. `command` looks set to be the same as discussion in https://github.com/whatwg/html/issues/11148 has stalled.

Having pointer & key events compose makes sense, and changing that would create similar issues as iframes, which create 'black holes' for pointer events. I think `focus` and `blur` makes sense composed too, but I'm less sure there.

The `attachShadow` and `<template>` additions make sense to me. I don't think the static property is the right approach, as it's a feature of the shadow root rather than the custom element.

Ideally the API should make it easy to 'conceal' `input` and `change`, and possibly `command` too if we don't get to make that change in time. So perhaps that would be the behaviour if `true` is the value, but allowing an array of event names seems ok too, eg if you want more control over `focus` and `blur`.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1368#issuecomment-2792221136
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1368/2792221136@github.com>