jQWidgets Forums
jQuery UI Widgets › Forums › Grid › Grid scrolling compatibility issue with webkit browsers
This topic contains 5 replies, has 2 voices, and was last updated by Doare 12 years, 7 months ago.
-
Author
-
Hi everyone.
I am experiencing a bug in webkit browsers (Google Chrome and Safari) in terms of scrolling. I’m using the latest version of jQWidgets (2.5.5).
The grid is implemented is a webpage among other information. When using the default window scrollbar to, say, reach the grid’s position, the new pointer position is not taken into account by the grid. If I have to scroll half a page to reach my grid, the grid will consider my pointer is still half a page up, instead of hovering its rows.
You can reproduce this behaviour pretty easily with a grid at full height: even the slightest scroll from the window scrollbar makes the gap obvious.
This only happens in webkit browsers.
Thanks in advance for your help.
Hi Doare,
Thank you for the feedback.
Could you please provide more information about the versions of Chrome and Safari that you use and also your OS?
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comHi Doare,
Just tested the Grid with Chrome 23.0.1271.95 m and Safari 5.1.7. I wasn’t able to reproduce the reported behavior regarding jqxGrid. Would you be able to send us a sample to support@jqwidgets.com which demonstrates the behavior?
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comHi Peter.
I’m running Windows 7 64 bits (Professional Edition), with also Chrome 23.0.1271.95 m and Safari 5.1.7.
Yes, I’ll prepare a sample and send it, then.
Edit: My description of the bug maybe wasn’t accurate, now that I’ve looked back to my results. If I scroll down, the grid thinks my pointer is lower than it’s supposed to be, actually.
Hi Doare,
The project uses jQWidgets 2.5(checked the header of the jqx-all.js file). The reported issue is already resolved in jQWidgets 2.5.5.
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comHi Peter.
Thanks a lot for your answer, the issue is indeed solved. I was sure to be up to date, I guess I should recheck properly next time.
Thanks again for your time!
-
AuthorPosts
You must be logged in to reply to this topic.