Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>"Nice" to see someone with the same problem. </p> <p>I opened your example and clicking on rows or checkbox performs badly with UI 1.8.</p> <p>We (php project, data locally stored in a JSON-variable, locally processed (sorting, filtering), no paging, up to 1000 records at once) were faced with the same problem and did not find a solution yet. UI 1.7 performs nice in any browser, but with the change to 1.8 we noticed some heavy performance issues with only firefox (3.6, no lower version tested). IE6, our other supported browser works fine (at least this time :-)</p> <p>I tried to find out the root of this problem and used firebug to profile the runtime of different functions called after the click. I know there is a different event handling by jquery for different browsers (normalization), but I do not knwow if this has any impact.</p> <p>The result can be be found here: <a href="http://tinyurl.com/24l8h54" rel="noreferrer" title="profile.png">profile.png</a></p> <p>Maybe you see anything noticeable in this list.</p> <p>As we also did not find any solution to this, we downgraded to UI 1.7.3 (which comes up with other but minor problems).</p> <p>Kai</p> <p>edit: Did you report this problem in the jqGrid forum? Most problems will be at least approached.</p> <p>edit2: Ok, after some further investigations and some research I found a workaround. As described here (<a href="http://www.trirand.com/blog/?page_id=393/bugs/compatibility-bug-with-jquery-ui-1-8-4/" rel="noreferrer">http://www.trirand.com/blog/?page_id=393/bugs/compatibility-bug-with-jquery-ui-1-8-4/</a>), the problem can be (temporarily) solved by removing the following line from the UI's css:</p> <pre><code>.ui-widget :active { outline: none; } </code></pre> <p>I can confirm that there's no performance issue anymore after removing this line. As this rule has no effect to our style, the workaround becomes a fix for us... :-)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload