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 example for components, the parent class is .bs-example and there are 2 children. One is .btn. From looking at the output, it looks like this will pull out just the element that contains a .btn class that's within an element with .bs-example. But it doesn't pull out the html elements between those 2 elements.
If you look in the _demo/components.html file, you'll see what I'm talking about when you get to the first .bs-example element. It's wrapping a button group, but the results are only the button elements.
I'm just posting this here to clarify... is this the intended use? Or do you expect to get the entire html element starting at the .btn-example?
The text was updated successfully, but these errors were encountered:
to your point though, you could specify it so that everything inside the .bs-example is pulled out. I was intentionally hard-coding some conventions to keep it simple, but I guess we should make it flexible enough to do that.
In the example for components, the parent class is
.bs-example
and there are 2 children. One is.btn
. From looking at the output, it looks like this will pull out just the element that contains a.btn
class that's within an element with.bs-example
. But it doesn't pull out the html elements between those 2 elements.If you look in the
_demo/components.html
file, you'll see what I'm talking about when you get to the first.bs-example
element. It's wrapping a button group, but the results are only thebutton
elements.I'm just posting this here to clarify... is this the intended use? Or do you expect to get the entire html element starting at the
.btn-example
?The text was updated successfully, but these errors were encountered: