ParamQuery grid support forum

General Category => Help for ParamQuery Pro => Topic started by: MatsP on October 19, 2013, 05:33:49 pm

Title: Infinite scrolling problem with IE
Post by: MatsP on October 19, 2013, 05:33:49 pm
I'm using option "flexHeight: true", which means the grid will be as high as the number of rows. I can't use Paging or flexHeight: false

The problem I'm having, is that when the grid is higher than the browser height, and you scroll down and click on a row, the whole grid jumps up or down. It doesn't stay where I just clicked.
To recreate the problem, I tested with the "Infinite scrolling" demo code from paramquery.com/demos, which uses the Base version (the Pro version has the same problem). I change the code to:   flexHeight: true.

The problem only occurs in IE (IE9 & IE10 tested), Firefox doesn't have the same problem. I have not tested other browsers.

I don't know if this is a similar problem:
http://stackoverflow.com/questions/14979365/table-scroll-bar-jumps-up-when-table-receives-focus-in-ie

Any thoughts on how this can be fixed?

Title: Re: Infinite scrolling problem with IE
Post by: paramvir on October 23, 2013, 09:43:35 am
The new Pro version 2.0.2 solves this issue.

Please see whether the fix works for you.
Title: Re: Infinite scrolling problem with IE
Post by: MatsP on November 02, 2013, 02:42:55 pm
This problem was fixed in the 2.0.2 version, but seems to have come back now when I upgraded to IE10 (which came with Windows 8.1).
Title: Re: Infinite scrolling problem with IE
Post by: paramvir on November 05, 2013, 12:06:07 am
Mats

I also found this issue in IE.

I'm working on the fix.



Title: Re: Infinite scrolling problem with IE
Post by: MatsP on November 06, 2013, 07:24:01 pm
Sorry, I meant IE11 of course (which came with Windows 8.1)
Title: Re: Infinite scrolling problem with IE
Post by: MatsP on November 11, 2013, 07:51:01 pm
Do you have a date when this will be fixed?

Thx.
/Mats
Title: Re: Infinite scrolling problem with IE
Post by: paramvir on November 12, 2013, 08:20:50 am
MatsP


The fix would be available in upcoming version by next week.