From what I can gather, this sort of error happens in MANY javascript environments that try to load a local file using ===>
file:///somePath/someFolder/someFile
In my case, as you will see, I have used the LINK property of the NAV LINK object which allows you to navigate to the html file (which are all in the same folder)
But when I run the project in PREVIEW mode, and click one of the Nav links (on any page) the Javascript error icon shows an error which indicates that it is NOT ALLOWED to load the target html file AND the error shows the entire filepath including the leading file:// (as opposed to showing it as a relative file. The class for the link shows the target as a relative file (i.e. same folder so its simply the file name.)
And BTW, I tried loading one of the DEMO projects and added an actual target to one of their Nav Links with the same result.
The bad news is that I reproduced your actions and got the same results
So I’ll be forwarding you changes and additions through the years that you can incorporate and test for me
It must be something local to my environment. Another weird thing is that If I launch my home page (index.html as a FILE://) in Chrome, EVERYTHING works as expected; so its something about the PREVIEW MODE in the Wappler IDE that’s getting stuck.
Is there any way for me to get under the covers like you can with Chrome INSPECT so that I can see exactly where this javascript error is occurring in WapplerLand? If the GUI is going to tell me about Javascript errors, then it should let me see more that the error message.