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
In the current configuration, we add the <button> element inside the .popover-body > div container.
<divclass="popover-body"><divstyle="display:contents;"><!-- user content here --><buttontype="button" aria-label="Close" class="btn-close" style="position:absolute; top:0.6rem; right:0.25rem; width:0.55rem; height:0.55rem; background-size:0.55rem;"></button></div></div>
It'd be helpful to keep the .popover-body to just having user-supplied content. The close button could be a sibling of .popover-body without changing appearance or (probably) behavior. The goal is that users should be able to write rules like .popover-body > div > :last-child to target the final (or first) content element in the popover.
In particular, I wanted to do something like
.popover-body>div>:last-child {
margin-bottom:0
}
The text was updated successfully, but these errors were encountered:
In the current configuration, we add the
<button>
element inside the.popover-body > div
container.It'd be helpful to keep the
.popover-body
to just having user-supplied content. The close button could be a sibling of.popover-body
without changing appearance or (probably) behavior. The goal is that users should be able to write rules like.popover-body > div > :last-child
to target the final (or first) content element in the popover.In particular, I wanted to do something like
The text was updated successfully, but these errors were encountered: