Ask Questions and Find Answers

Hey Dominik!

In other instances of this, we've always concluded that some exception was being thrown by custom code (and caught by Senna) resulting in that endless loading.

First thing I'd try is to enable the "Pause on caught exceptions" setting in your DevTools and see if that points you to the right place.​​​​​​​

Thanks Chema for your help.

I was able to track it down to a Javascript error inside our templates.

So if I understand you correctly everytime a Javascript error occurs on a page that "Oops"-message is shown? Why? That message does not give a normal user anything, the user cannot do anything about it. 

Maybe a better message would be something like "Hey visitor! The following (Javascript) error occurred: <message here>. Please inform the administrator of this website".

Hey Dominik!

You are indeed correct... we could do a better job at messaging the issue. The problem if I remember correctly is that we have some try-catch block when evaluating incoming scripts that might make the navigation stop, thus showing the "Ooops" message.

Since this has happened mostly at development time, we haven't fully explored what would be a better option. I don't think showing a stacktrace to the end user would be benefitial at all, but maybe we could log the error in the console so developers are properly notified and show a friendly error message instead of leaving the user hanging in a never-ending loading.

Could you maybe provide a simple reproduction case so we can study that in context and try to come up with a friendlier solution?
Thanks!

Hey Chema,

I think the most simple test case is the following. Just put the following snippet in a page (using a template or something like that) and navigate to a new page afterwards.

Liferay.on('endNavigate', function() { throw "error!"; });