Clarify or change behavior of Tabs in CSS/JS about mui HOT 3 CLOSED

Thanks for the update! I expected to see the error on page load so I got confused initially.

I fixed this bug and published a new version (0.10.3). Now clicking on a tab will activate that tab without triggering the error. I also considered activating the first tab by default if ".mui--is-active" isn't present but that raises other issues that I hadn't considered (e.g. what if related pane is dynamic and isn't present in DOM) so I'm leaning towards leaving it as-is.

Let me know if you run into any more problems with the tabs component!

from mui.

It should be fairly easy to modify the JS code to activate the first tab by default when "mui--is-active" is not set. I can take a look at this. In the mean time, can you share some example code to reproduce that error message? I tried the html but I don't see an error message (Chrome/Firefox/Safari):
https://jsfiddle.net/muicss/dku8f2ar/

from mui.

Tested on: Chrome 83, Firefox 76, Edge 44, Safari 13.1

Your fiddle https://jsfiddle.net/muicss/dku8f2ar/ I get the same error in console (in all browsers listed above).
Clicking on FAQ or Contact Form does nothing.

Uncaught TypeError: Cannot read property 'id' of null
    at s (mui.min.js:1)
    at HTMLAnchorElement.r (mui.min.js:1)

Another thing to note is that I tested Safari 13.1 inside a VM as to rule out some weird esoteric setting on my laptop. 😆

from mui.