Cube Grids Screens issue – Rows misalignment

[dastagiri89]

Hi Team,

I am facing issue with cube grid rows misalignment. When I scroll down to last record as attached snapshot rows are missed and there is a huge misalignment of rows.

FYI .. I have used resolution as 1912*984 and Chrome browser Zoom to 100%. However this issue was occurring worst when zoom to 125% or 150%.

Can you please provide solution and fix details for this. Happy to share more information if needed. Thank you.

Thanks

[Isomorphic]

See Browser Zoom in the docs to understand the limited support that is possible for zoomed browsers.

As far as this happening without zoom, this isn't reproducible in samples even if you configure the sample to maximize the number of rows ("Scenarios" as only column facet). You may have external CSS that is creating the issue. Let us know if you can make it reproducible.

You also forgot to include your version information, which is always required - please make a note of this. And, you should test against the latest patched build before posting, to ensure you are not looking at an already-fixed issue.

[dastagiri89]

Hi Team,

Thanks for the response.

We were using version of 6.1p20170630. I am able to reproduce the issue using your samples. Below are few steps which I have followed.

1. https://www.smartclient.com/smartgwt...se/#cube_basic
2. Browser : Google Chrome (No Zoom in Chrome (100%))
3. Operating System : Win 10
4. Display : 125%. (check for attached snapshot for win resolution)
5. Attached snapshot is for “Advanced Cube Grid”. Even bug is reproduced in “Basic Cube Grid” as well.

Can you please provide solution for this. Please let us know if you need any more details. Thank you.

Thank you.

[Blama]

Hi dastagiri89,

here two pretty old threads about system zoom, which suggest that system zoom might result in visual glitches: 1, 2. I do not know what Isomorphic's position on system zoom is, because here they say they can't detect it, but that it can introduce browser bugs.

Best regards
Blama

[dastagiri89]

Thank you Blama for your reply.

Isomorphic : “The cube grids rows misalignment cannot be reproduced with a 1912*984 resolution– 150% display, nor a 1912*984 resolution– 100% display (but with this display, it is impossible to work as it is too small). This issue is mainly visible with a 1912*984 resolution– 125% display.
And this configuration is used by many users, so it is really blocking.
Thanks in advance for your feedback.
Best regards.”

[dastagiri89]

Hi @Isomorphic ,

Could you please tell us what are the Isomorphic positions on system zoom ? Currently many of users are using 1912*984 resolution - 125% display and facing difficulty with rows misalignment. We need your support with high priority as this is really a blocking for us !

Thanks in advance
Best Regards."

[Isomorphic]

We are double-checking, but it is likely that what is going on here is the same as for browser-level zoom: Chrome / WebKit simply reports various coordinates and sizes wrong, and not in a consistent manner, so no workaround is possible until the various Chrome bugs noted in our docs are fixed.

Starring those issues could help notify the Chrome team that this continues to be a problem.

Note that, in our testing, this issue was just cosmetic: there is slight misalignment but all data was reachable.

[Isomorphic]

We are finding that the issue is only reproducible for some people and not others. It's not clear yet what the difference is, but you should retest after disabling any Chrome extensions and reverting any non-default settings applied, even if you feel sure those settings could not cause the issue.

[Isomorphic]

Hi @Isomorphic ,

Could you please tell us what are the Isomorphic positions on system zoom ? Currently many of users are using 1912*984 resolution - 125% display and facing difficulty with rows misalignment. We need your support with high priority as this is really a blocking for us !

Thanks in advance
Best Regards."

As mentioned, the cause of this is a Chrome browser bug, but if you can star the defect report covering this issue, and perhaps leave a comment indicating how it's affecting you, we might get them to raise the priority.