Since it is now a globally-recognized element, it's treated as a first class citizen in
the DOM, receiving full type support when using<filter-input> directly in your code,
or adding event listeners, and so on.

Note: today I learned that renaming a branch after opening a PR immediately closes that PR. Sorry for the dupe 😞

feat(types): addfilter-input to HTMLElementTagNameMap

c4a6e6c

Adding `filter-input` to the global `HTMLElementTagNameMap` interface is the type-level equivalent of registering the tag in the global registry. Since it is now recognized as a globally-available element, it enables stronger types when using `<filter-input>` directly, or adding event listeners, etc.

nberlette requested a review froma team as acode owner

April 17, 2023 12:55

Copy link

primer-css commentedApr 17, 2023

👋 Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

🎨If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
⏩If this is a PR that includes changes to an interaction, please include avideo recording in the description.
⚠️If this is urgent, please visit us in#primer on Slack and tag the first responders listed in the channel topic.