Has anyone using 9.1 tag libraries in building blocks also encountered problems with //@ in their javascript files?

Reply

Lum Hon Peng Posted: 26 Jul 2012 11:42 PM

rated by 0 users

Hi,

Just though i check if this is a known item to avoid. I had been working on a requested building block. Javascript files included via JSFile. Works fine in Chrome & Firefox. In IE 8, problems occurred, javascript not working - traced to a file. Errors were "expected ';' ".

Same javascript tested fine in tomcat, standalone - without any tag libraries. So I reverted to earlier version and slowly merge changes from the recent.

Found that presence of //@ - (e.g. //@param xxxxx - blah blah <description for parameter> ) was the cause. Removed it and the error no longer appeared in IE. 

Does anyone know if //@ is a reserved word in the tag lib / prototype javascript framework?

Other Things Note:

• Before and after resolution, I has jQuery framework loaded as well, and used jQuery.noConflict(); to relinquish control to prototype.
• Was using <bbNG:jsFile ...> but changed to <javascript language='javascript' type='text/javascript'>
  • Read somewhere that IE is picky about javascript tags without the language='javascript'
  • Wasn't the cause.

Thank you.

Regards,

Lum

Reply

Tas replied on 29 Jul 2012 10:25 PM

rated by 0 users

I have seen some abnormality on IE, but not on Chrome and Firefox, where page layout is a bit messed up and course TOC javascript stopped working. I did not go to far into diagnosing the issue, but adding the HTML 4 doctype solved this issue I had. Don't know if it is going to help you or not but worth a try.