Links of subnav are not clickable sometimes

[jstet]

I am currently not able to reproduce the conditions under which this happens

[jstet]

Only seems to happen locally, will just close it as nobody noticed this in live version

[jstet]

This just happened to me on the live page :S

[KonradUdoHannes]

Is the issue gone on refresh? This would hint at one component not loading properly sometimes. Either way we can include this as a test in #240 and see whether it pops up there (worst case only sometimes). to analyze it further.

Any particular links that did not work, or was it all the sub nav links?

[jstet]

What do you mean with gone on refresh? The links in all dropdowns, including the language dropdown, did not react. No error messages in console.

[KonradUdoHannes]

With gone on refresh I mean, that the links work again once the page is refreshed.

I think we can get connection issues that can cause this. I had the same issue, but usually in connection with major setup problems affecting connection. In such cases the js for the entire site did simply not load. That is why I'm wondering whether a reload fixes it (at least with high probability) for the occasional case if the cause is some failed svelte initialization request in the background.

Also if a http requests fails it might sometimes not show up in the console. The network tab would show it, but this has to be running in advance, which makes it hard to use for occasional issues.

[jstet]

Yes a refresh fixed it :O

[KonradUdoHannes]

I had the issue a couple of times now, and my impression is the following.

• It happens when there is an error related to reactivity of svelte, in particular I noticed it when components update reactively (because a property changes).
• If the component is already loaded and a reactive update throws an error, some JS promise build into svelte fails and as a result js on the site is crashed/stuck until refresh
• Error level logging in the browser helps to diagnose the respective problem
• This issue does not seem to a specific bug but rather a generic symptom of a whole range of different bugs, which can be as simple as typos in components or configuration issues in the cms.
• Fixing the underlying issue that caused the respective promise to fail fixed the reactivity of the site again. So there is probably not much to do here except for increasing general robustness and error logging of the application.

Because of the last two point I would suggest closing this issue and try to treat the underlying causes individually if this symptomatic behavior appears again. @jstet do you agree?

[jstet]

Thanks for investigating!

What was "the underlying issue that caused the respective promise to fail"?

What do you mean with error level logging? If we know how to identify the underlying problems then yes I'd also close this issue.

[KonradUdoHannes]

@jstet

The problem in my case where simply parsing errors, like some required parameter being undefined, that I introduced and later removed while refactoring cms parsing.

With error lebel logging I mean that the console has 5 different logging levels. .error (typically red), .warn (typically yellow), .log , .info and .debug. For me the issues where related to logged errors, which are usually also the most severe. The only thing to keep in mind is that the browser dev tools usually let one filter for the type of messages one sees, so one has to make sure that errors level logging does indeed show up.

I'll close the issue. If we encounter the problem again without being able to diagnose the underlying cause, we can reopen it.