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

ITenthusiasm left a comment (whatwg/dom#1368)

> Ideally the API should make it easy to 'conceal' input, 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.

Yeah thinking about it a little more, I think an array of values might be ideal for people who only want to conceal specific events. And perhaps `true`/`"all"` could still be allowed to represent concealing everything? Providing a more general solution like this out of the box might help prevent issues similar to this one from being brought up in the future.

If it's possible to group events into categories, then another option might be to have pre-defined strings that capture certain groups of events. For example `concealEvents: ["form"]` could conceal things like `input`/`paste`, etc. I'm not sure how maintainable that concept would be, though. And I imagine most people would know the specific events they'd want to block.

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

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