You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I try to reuse a component on the same page by copy/pasteing some HTML, needing to look through the markup and update every id and commandfor is somewhat laborious and error-prone. Both the "close" and "hide-popover" commands will very often be used to close the parent popover/dialog that the button is nested within.
It might be useful to be able to refer to the nearest ancestor popover/dialog element, rather than only being able to specify an id, which needs to be unique every time.
Something like commandfor="parent" or commandfor="nearest".
Needing to reference a unique id makes reuse awkward.
The text was updated successfully, but these errors were encountered:
o-t-w
changed the title
[invokers] Reference parent?
[invokers] Reference the parent popover/dialog
Feb 2, 2025
For certain UI components, like a large nested menu, for example, many buttons, each with a
command
andcommandfor
might be used.https://codepen.io/cssgrid/pen/raBbMPL
If I try to reuse a component on the same page by copy/pasteing some HTML, needing to look through the markup and update every
id
andcommandfor
is somewhat laborious and error-prone. Both the "close" and "hide-popover" commands will very often be used to close the parent popover/dialog that the button is nested within.It might be useful to be able to refer to the nearest ancestor popover/dialog element, rather than only being able to specify an
id
, which needs to be unique every time.Something like
commandfor="parent"
orcommandfor="nearest"
.Needing to reference a unique id makes reuse awkward.
The text was updated successfully, but these errors were encountered: