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
Is the _element property intended to be considered private? That generally is the case but I wasn't seeing it specifically called out anywhere in this repo. I ask because I have a small third-party library I am considering consuming that eases the dynamic generation of Toasts, however the element that is passed to the constructor of bootstrap.Toast is created in the library code and not exposed to the consumer. So my only way of attaching a handler on the component would be to call myToast._element.addEventListener("hidden.bs.toast", ...). Thanks for your input!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is the
_element
property intended to be considered private? That generally is the case but I wasn't seeing it specifically called out anywhere in this repo. I ask because I have a small third-party library I am considering consuming that eases the dynamic generation of Toasts, however the element that is passed to the constructor ofbootstrap.Toast
is created in the library code and not exposed to the consumer. So my only way of attaching a handler on the component would be to callmyToast._element.addEventListener("hidden.bs.toast", ...)
. Thanks for your input!Beta Was this translation helpful? Give feedback.
All reactions