With this understanding, I have made a lot of scripts, and it seems that I have never encountered any problems, so I am more confident in my original judgment. Once again, the results are implicitly calculated by IE. The mixed use of the encode script and the normal script is neither a problem nor a problem, but a problem may occur under specific conditions. See the following example:
Copy codeThe Code is as follows: <Head>Var o = new Object ();
Try {o. Message ();}
Catch (e) {WriteLine ('call "object' + msg + e. message );}
Try {Object. Message ();}
Catch (e) {WriteLine ('call "Object. Message" Fail. <br> '+ e. message );}
Var e = new Encode ();
Try {e. Message ();}
Catch (e) {WriteLine ('call "encode' + msg + e. message );}
Encode. Message ();
Var n = new Normal ();
Try {n. Message ();}
Catch (e) {WriteLine ('call "Normal '+ msg + e. message );}
Normal. Message ();
</Script>
</Body>
</Html>
Save the above Code as a *. htm file. The result is as follows:
Call "Object. prototype. Message" Fail.
Object doesn' t support this property or method
Call "Object. Message" Fail.
Object doesn' t support this property or method
Encode. prototype. Message
Encode. Message
Normal. prototype. Message
Normal. Message
The above two jscript. encode codes are simple: Object. prototype. Message = function ()
{
Alert ('object. prototype. message ');
};
Object. Message = function ()
{
Alert ('object. message ');
};
Function Encode (){}
Encode. prototype. Message = function ()
{
WriteLine ('encode. prototype. message ');
};
Encode. Message = function ()
{
WriteLine ('encode. message ');
};
If we replace the above two sections of code with the two jscript. encode sections in the html, the subsequent operation will not cause any exception and the output will be: Object. prototype. Message
Object. Message
...
The above code examples have explained in detail the problem of the encode script code. That is, the prototype method and static method imported to the built-in JScript object cannot be referenced in non-encoding scripts. The Object in the above example is a built-in Object of JScript. We have imported a prototpye method and a static method Message () respectively (). For non-built-in object Encode, the prototype and static methods imported in the encoded code can be normally accessed in the non-encoded code.
So how to access the import method of built-in objects? In fact, the solution is not complex, but complicated. We need to use some wrapper methods to put them together with the encoded code so that we can access them in the non-encoding code. For example, we can wrap the above Object as follows:
Object. prototype. Message = function ()
{
WriteLine ('object. prototype. message ');
};
Object. Message = function ()
{
WriteLine ('object. message ');
};
Var obj = new Object ();
Function ObjectPrototypeMessage ()
{
Obj. Message ();
}
Function ObjectMessage ()
{
Object. Message ();
}
In this case, we can use wrapper methods such as ObjectPrototypeMessage and ObjectMessage to access the built-in object import method in the encoded code.
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
