46 fleshes out the proposed close button API. The names there are:

closebutton="" attribute on std-toast, used as either <std-toast closebutton> or <std-toast closebutton="Dismiss">
el.closeButton JS property reflecting the closebutton="" attribute
closeButton: true or closeButton: "string" as a showToast() option, behaving the same as the JS property
::part(closebutton) { ... } in CSS to style it

We could potentially use different names here, e.g. closeable or close or dismissable or similar. We could also change the ::part() name independently from the attribute/property/showToast option name.

Thoughts welcome!

jackbsteinberg / std-toast

Close button API naming #47

46 fleshes out the proposed close button API. The names there are:

46 changed substantially before landing in a way where it seems much more obvious `closeButton` is a reasonable name. The only potential confusion left is that one might expect `el.closeButton` to return a button element, instead of the string or boolean value it's currently specified to do.

jackbsteinberg / std-toast

Close button API naming #47

46 fleshes out the proposed close button API. The names there are:

46 changed substantially before landing in a way where it seems much more obvious closeButton is a reasonable name. The only potential confusion left is that one might expect el.closeButton to return a button element, instead of the string or boolean value it's currently specified to do.

46 changed substantially before landing in a way where it seems much more obvious `closeButton` is a reasonable name. The only potential confusion left is that one might expect `el.closeButton` to return a button element, instead of the string or boolean value it's currently specified to do.