Bug: High CPU usage with hidden grid(s)

There is a possibility with 1.0.1 or earlier versions of the grid library that CPU % usage will stay high even after initial page rendering. It can happen if you have several hidden grids on page and you are using 'display:none' rule to hide either the grid itself or its parent element.

The issue is related to the grid code which tries to calculate the size of the scrolling area. When the grid size is 0 (which is true both during initial rendering and also when display:none rule is applied) the calculation starts again after 500ms delay and this may trigger high CPU usage if you have several grids on page.

This is a bug and it will be corrected in 1.0.2

Possible workaround is to use 'visibility:hidden' instead of 'display:none' as it will allow correct size calculations.

Most likely this post is related to the same issue:

http://www.activewidgets.com/javascript.forum.1931.15/cpu-usage-is-still-very.html

Hello, thanks for that info, but question, does this pertain to the client's cpu usage or the server's?

Clients. There is no server side processing with AW, it is a Client Side JavaScript Framework.

tks.