jquery autocomplete performance

Here's a very simple piece of code, $ (function () { var flag = false; $ ("button"). Click (function () { if (flag) { $ ("P"). Text ("true"); Flag=false; }else{ $ ("P"). Text ("false"); Flag=true; } }); }) With the data () method instead, the code is as follows: $ (function () { $ ("button"). Click (function () { if ($ ("P"). Data ("flag")) { $ ("P"). Text ("true"); $ ("P"). Data ("flag", false);

The reason is that when I was testing: I brought in the wrong variable. For details, refer to the $ (parentID> childClass) on the image. I have compared the two characters to change the size! Thanks to "No cupid" in the html5 Chinese Web QQ group ". The third point mentions the relationship between the parent element and the child element and mentions the use case for selecting the child element from the parent element:Copy codeThe Code is as follows: $ ('. child', $ parent)$ Parent. find ('

The reason is that when I was testing: I took the wrong variable. You can view the $ (ParentID > ChildClass) on the picture directly I compare two characters to change the size! Thank HTML5 Chinese QQ Group in the "No Cupid". The 3rd reference to the relationship between the parent element and the child element refers to the use case that selects the child element from the parent element: Copy Code code as follows: $ ('. Child ', $parent) $parent. Find ('. Child ') $parent.

From the jquery website, a simple translation, a few of the usual improvement methods:1: Add outside the loop (Append Outside of Loops)For example, code 1:Code 1 Checklist:function (I, item) { var newlistitem = "; " #ballers " ). Append (Newlistitem); });Because DOM operations bring overhead, the DOM is manipulated every time the loop operates, and performance is poor. It is recommended to use a str

The jquery Performance Tuning Guide can be considered in the following 12 directions. 1, always inherit from ID selector 2, use tag (sign) before class 3, cache the jquery object (in multiple use, instead of using an intermediate variable, instead of always with a selector)4, restrictions on direct DOM operations 5, pay attention to minimize event bubbling 6,