We want others to be unable to modify the purpose of JS encryption, so we can work hard on JS complexity and use modular development. This function references that function, this object inherits from that object ..... and soon others will be dizzy ....... of course, you will also be dizzy when debugging or modifying it yourself .......... let me talk about it ..... don't hit me...
In fact, what I want to say is that if you don't want others to modify it, you can add a validation check on many JS locations. If not, so we can call it here to get rid of others...
Of course, whether this check is concealed or not, and whether it is perfect after the check is not metProgramI just gave an idea. The following is an example. I just want to express my thoughts ......
IE only<! -- The following code can be modified -->
[Ctrl + A select all Note: If you need to introduce external JS, You need to refresh it to execute]
FF only<! -- The following code can be modified -->
[Ctrl + A select all Note: If you need to introduce external JS, You need to refresh it to execute]