Repository navigation
Make active tab behaviour independent of html structure #20156
Description
Activity
I'm running into problems with this, as well, but perhaps in the opposite direction. In most cases, putting
activeon the item withnav-itemworks, but in some cases like tabs, it needs to be on thenav-link. On the surface, it appears inconsistent, but I may not be seeing the pattern. Understanding this is important for ember-bootstrap, where we're re-implementing the JS behaviors in an Ember-y way.
In v4, the active tab selector is defined as:
The first selector forces us to use the
nav-itemclass for the tab, which I would like to avoid in my case.The second selector, which applies to the tab, not the link, doesn't seem to work correctly (see #18566)
Is the descendant selector really needed?