Forum Moderators: open
The only pupose of the MOTW comment is so the active script can run locally without the annoying popup...
Not the only purpose; ALL the settings of that security zone will apply. Which is a reason why web pages could well behave differently when run 'locally' as opposed to from a web server.
Yes I did put the comments on the page that I linked to, but now that I understand the purpose of the comment I see that would make no sense.
If you understand the purpose of the 'comment' (ie. MOTW) why does it make no sense? Strictly speaking, in IE the MOTW is not a comment, it is a special instruction, just like conditional comments. Yes, in other browsers it is treated as an oridinary comment.
It would be interesting to see if someone can duplicate the problem.
Yes, I can duplicate the problem, but under the following scenario I can solve it by including a MOTW on every page:
- In IE, running in the local security zone.
- Two pages, PageA and PageB.
- PageA has a link to PageB.
- Without a MOTW on any page, the link from PageA to PageB works OK.
- Add a MOTW to PageA, the link from PageA to PageB does NOT work.
- Add a MOTW to PageB, the link from PageA to PageB works OK. Sorted.
If in your environment this does not solve it, then I guess there must be something else?!
That last comment (//end AC code) is just a plain ol' JavaScript comment.