DotVVM Bootstrap Extension: Unhandled Exception in JS

Dear DotVVM Team,

We are facing once in a while and currently quite often unhandled exceptions when debugging our DotVVM application which seem to come from the Bootstrap4 extension. This is quite annoying to the extent it is happening right now. In the following i have a screenshot of the place where it is thrown.

Do you have an idea what the issue could be? I have the feeling that this exception gets thrown whenever we are using the TabControl, but in the HTML we cannot find an obvious error regarding CSS classes there:

Kind regards

Daniel

Thanks for the report. I tried to reproduce it internally, but I don’t have such an error on any of our usages of TabControl.

  1. Can you provide the stack trace for the error? It would help us to see if it is really TabControl or some other component.
  2. What is the version of DotVVM.Controls.Bootstrap4 package you use?

Thank you for your reply.

Clicking on “Copy Details” in the exception pane, this is what i am getting:

Message=
Source=
StackTrace:
at dotvvm.extensions.bootstrap.transformClassesToSelector (http://localhost:80/subPath/dotvvmResource/dotvvm–bootstrap/dotvvm–bootstrap:3168:36)
at HTMLAnchorElement. (http://localhost:80/subPath/dotvvmResource/dotvvm–bootstrap/dotvvm–bootstrap:2897:58)
at HTMLAnchorElement.dispatch (http://localhost:80/subPath/dotvvmResource/jquery/jquery:2:41964)
at v.handle (http://localhost:80/subPath/dotvvmResource/jquery/jquery:2:39983)
at Object.trigger (http://localhost:80/subPath/dotvvmResource/jquery/jquery:2:62230)
at HTMLAnchorElement. (http://localhost:80/subPath/dotvvmResource/jquery/jquery:2:62825)
at w.each (http://localhost:80/subPath/dotvvmResource/jquery/jquery:2:2765)
at w.fn.init.each (http://localhost:80/subPath/dotvvmResource/jquery/jquery:2:1438)
at w.fn.init.trigger (http://localhost:80/subPath/dotvvmResource/jquery/jquery:2:62801)
at l (http://localhost:80/subPath/dotvvmResource/bootstrap/bootstrap:6:73831)

The version i am using is

image

I do not know exactly whether it is directly related to the TabControl, but there is at least always a tabcontrol somewhere around, when the error is been thrown.