anchor.js and site.js files are not loaded

[niklauslee]

Doc files are generated successfully, but I can't expand folded instance member items in chrome browser. It seems anchor.js and site.js are not loaded in the browser.

I had checked in the chrome's dev tools. The elements <script src='assets/anchor.js'></script>
and <script src='assets/site.js'></script> are removed in the DOM tree.

I've also tried to load via http-server the doc files, not directly from the local files. But, the problem still exists.

It may not the problem of documentation.js, but I need help.

There generated doc files are attached.
docs.zip

Any ideas?

[tmcw]

Hmm, I'll look into it - are you using Windows? There may be an issue with path separators.

[anthony-redFox]

Windows 10. Chrome 59.0.3071.115.

I have error message 'Cannot read property 'getElementsByTagName' of null' from 'site.js'
@niklauslee you move 'script' tags to the head thats why you get the error.
Originally script tags should be before 'body' close tag.

@tmcw I think, issue can be closed.

[niklauslee]

@anthony-redFox Oops! Sorry, I attached wrong files. It was an trial to resolve the problem. I attached the original files ('script' tags in the end of 'body' tag) generated from documentation.js.
docs.zip

@tmcw I'm using Mac OS (Sierra) and Chrome (59.0.3071.115)

[anthony-redFox]

@niklauslee you have not valid html file that why script are not loaded.
You have html tags <user> <email> <url> and etc in description which should be escaped.

"Returns the full path of the default user extensions directory. This is in the users
application support directory, which is typically
/Users/<user>/Application Support/StarUML/extensions/user on the mac, and
C:\Users\<user>\AppData\Roaming\StarUML\extensions\user on windows."

But should "Returns the full path of the default user extensions directory. This is in the users
application support directory, which is typically
/Users/<user>/Application Support/StarUML/extensions/user on the mac, and
C:\Users&lt;user>\AppData\Roaming\StarUML\extensions\user on windows."

@tmcw I think, it is a bug.

[tmcw]

I don't think this is a bug: for the documentation:

Returns the full path of the default user extensions directory. This is in the users
application support directory, which is typically
/Users/<user>/Application Support/StarUML/extensions/user on the mac, and
C:\Users\<user>\AppData\Roaming\StarUML\extensions\user on windows.

The path /Users/<user>/Application Support/StarUML/extensions/user should have tick characters around it, like in this line. Otherwise, Markdown generation correctly treats <user> as a HTML tag - that aligns to the standard and the expectations surrounding it.