Truncated DataGrid display in 2.5.1 - scrollbar shifted

Hi-
We're seeing a problem where the DG is loading and the columns to the right (horizontal scrollable) are not viewable because the horizontal scrollbar is already moved to the right. This happens with users that are remote to our site e.g. 100 plus miles away.

I think this implies slower loading of the DG.

I've applied the css fixes that were mentioned here on this forum for truncated DG display but still no luck.

thanks!

Difficult to guess - can you post an example which allows to reproduce this?

Alex-

Not really - it just happens with certain users who tend to be a distance from the site:

Horizontal rollbar is to the right, grid columns are truncated.

Alex-

How can I manually access the horizontal scrollbar and move it to the left?

Can you post a code snippet?

thanks!

I suspect this distance issue is a red herring. Even though they may be some distance away, the activity all occurs on the client's browser.

Otherwise, I'd be seeing problems visiting this site (which I believe is located in the UK somewhere and I'm browsing from Australia).

The two questions I would ask are -

1) What browser and version are they using?
2) What is their display size?

If these are all the same as what you're using locally, get them to try another browser first.

Thanks for the reply -

The problem occurs in IE but not FF. We are required, however, to support IE as part of our application.

It happens consistently when users access pages with DataGrids using IE 7 under Vista or XP. A partial DG will load with missing columns, as if the DG was interrupted. The reason I suspect there is some network latency is that there is a fair amount of data being loaded in the DGs from the server and the problem does not happen to users close to the site but always happens to users a distance away.

Here are some of the things I've tried, to no avail:

1. Calling scrollbar methods after the DG loads in order to hopefully position them to the left and top (works but still have missing data).
2. Spinning with a JS timer after the DG loads for 1 second+ in order to allow the DG to complete initialization.
3. Added the scrollbar css fixes mentioned for 2.5.1
4. Put explicit XML tags in the top of our XHTML pages as suggested for MS.

I wonder if there is an event in IE that is being fired that is messing up the DG load.

If anybody has an idea, please let me know. We are planning to go back to AW 2.0 if this doesn't work.

thanks
Max

The missing columns issue sounds rather odd. Since the data is obviously being transferred in rows, every column of each row should be there. Viewing the page source should confirm that (this, of course, depends on whether you embed the data or use AW's setURL() method to read it from a file).

I gather the page completes loading eventually. So perhaps it is related to latency in some way. From your comment about AW 2.0, I gather it worked correctly with that version?

How do you serve the data? With a CGI script or PHP or an MS method? Do you embed the data in an array in the page or do you call the setURL() method?

Are you able to do it in reverse order so that you can do testing at your end? I'm not even sure what's available for IE in terms of debugging.

Is your grid inside html <table> tag? Do you have any other scripts loading into the same table after the grid script? If yes, try moving loading the scripts outside of the table.

If you are using document.write(grid) - try changing to div.innerHTML = grid, possibly with some delay, maybe in window.onload.

Does it happen if you remove doctype?

Alex-
Yes, it is inside a table tag and other scripts are loading. We have several external drop-downs outside the grid. It won't be easy to move them but I can try. BTW, this was all working prior to 2.5.1.

I'm using DG methods to update the grid....setCellText etc.

There is a doctype tag in out template but if I remove it our pages don't work - we're using xhtml.

BTW, this does work in IE6; only breaks in IE7. I replicated the css changes for 2.5.1 (aw-ie6.aw.strict etc) to aw-ie7.aw.strict

I guess the grid size is set to 100% and there is a <script> tag, which loads external script, in the same table below. If this is the case then the grid initialization may fail because it happens while the external script is still loading. Until everything inside the table is loaded - IE reports all table/cell sizes as 0 and this will break the grid. This is a grid 'bug' and it will be fixed in the next release. In the meantime the solution is to delay grid initialization until everything inside the table is ready (i.e. use parent.innerHTML = grid and put this statement late enough) or move loading of the external scripts before the table tag.

Alex-
Do you know when this fix will be available?
thanks
Max