Don't know why this issue was closed

[carlosmintfan]

          Please reopen this if you closed it accidentally. 😃

Originally posted by @carlosmintfan in #40438 (comment)

Please check original issue and reopen if necessary.

[julien-deramond]

Hello @carlosmintfan
I've moved your issue to a discussion here.

I'm not sure if there's an issue in #40438, or I don't understand exactly what was reported.
In our Nav and tabs documentation:

• The entire first part of the documentation shows the effect of classes and DOM structure on the rendering, explains the concepts, but doesn't do anything dynamically. The developer has to switch the elements programmatically (e.g. .active class, aria-selected, etc.)
• The only dynamic part is explained in JavaScript behavior, and requires JavaScript.

If you think there's a use case where it doesn't work, you can create a new issue and integrate a reproducible live example with CodePen, StackBlitz, or any other tool, to make that more understandable :)

[carlosmintfan]

All right, I didn't test, and yeah, it's all the right behaviour, I just opened it in case the original issue was closed accidentally or whyever, the author just closed it without explaining...

[jipexu]

Hi
Yes no issue there.
For example the concept explained by @julien-deramond is the same for example in the navbar doc where the link are dead of course.....