If one interprets "ability to run scripts in your domain's browser context" to include the case where where your domain's browser context is explicitly broken so as to not allow scripts to actually do anything (i.e., not even execute any instructions), then it's still the case that everything your code can do, their code can do; it's just that since your code can no longer do anything, neither can theirs,…
… which, I suppose, is one way to achieve absolute security, but not terribly useful if you actually wanted to do anything in javascript.
In reply to Re^3: CGI::Ajax. Getting content of second.html file to resultant div of one.pl (same/cross domain)
by wrog
in thread CGI::Ajax. Getting content of second.html file to resultant div of one.pl (same/cross domain)
by msinfo
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |