Hi,
occasionally the visibility of the WHDG in one of our pages is set to "hidden", although the grid is present and has data rows. I can make the grid visible via firebug and everything is fine; therefore there should be no problem and no reason to make the grid invisible.
There is one error shown in the javascript debugger: "TypeError: this._scrollStyleSheet is null", nothing else.
The grid is placed inside a WebDialog control. I can close the dialog and reopen it, but the grid stays invisible. I have to restart either the application or the browser to make the grid visible again; clearing the browser chache does not work.
It seems that in version 12.1 an at least similar problem occured (see http://ko.infragistics.com/community/forums/p/69972/354306.aspx#354306 "infragistics is setting webdatagrid to visibility:hidden - version 12.1").
Is this a known bug and if so does a workaround exist?
Is there an easy way for a user to make the grid visible (i. e. not via firebug but via button click, javascript etc.)?
Hello Bernhardus,
Thank you for posting in our forums!
As Dave mentions in the forum thread you linked to, the WebDataGrid/WebHierarchicalDataGrid initially renders invisible to perform some calculations without affecting the appearance of the page. Once the calculations finish, we reset the visibility. In this case, the javascript error you are receiving is interrupting our calculations and preventing the visibility from resetting.
After some initial research, this error appears to be related to the ColumnFixing behavior. Could you please provide me with the following information to determine the cause of this:
1.) What properties do you have enabled on the WebHierarchicalDataGrid, particularly pertaining to your behaviors. Would you be able to provide the markup/code you are using for the grid?
2.) Are you receiving any HTTP errors with your network traffic while the page is loading?
3.) You said you are closing and opening the dialog and that the grid is visible after restarting the application or browser. Is the WHDG visible when you originally open the WebDialog? Could you please clarify the steps to reproduce this to better help me understand how to reproduce this?
Looking forward to hearing from you.
first of all I have to correct myself - in fact it is a WebDataGrid which is causing the problems, not a WebHierarchicalDataGrid. We once used the WHDG in this dialog, but for some reason we now use WDG. Sorry. Do we have to / is it possible to reassign this thread to the WDG discussion group?
Nevertheless, the page in question has a grid showing items which can be ordered. The user selects one or more items (data rows) and then opens the order dialog, which contains a WebTab with two tabs, the first one with a WebDataGrid showing the items the user had selected, the second one showing a WebDataGrid displaying material already in store which the user can decide to take instead of ordering new material. The second tab is disabled (not invisible) if there is no appropritate material in store, otherwise it is activated when the dialog opens. The grid on the second tab is sometimes invisible although it should not.
Concerning your questions:
1) The following behaviours are enabled (in code-behind):
2) There are no http errors. But there are lots of CSS hints in jquery.ui.custom.css and ig.ui.min.css like
Unknown property '-moz-border-radius'. Declaration dropped.
Selector expected. Ruleset ignored due to bad selector.
etc.
Also there is a SyntxError in ig.ui.min.js:
Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead
followed by an Error:
http://xxx/Scripts/ig.ui.min.js is being assigned a //# sourceMappuingURL, but already has one
Loading the dialog which contains the grid is no problem. If the grid is visible there is no error. If the grid is invisible there is the TypeError which I mentioned.
3) I know this is not what you would like to read (it's not what I'd like to read, for sure), but: I can't clarify the steps, because the error can be reproduced only erratically.
This is the WebTab containing the grids:
<ig:WebTab ID="ItemsWT" runat="server" Width="100%" Height="250px"> <Tabs> <ig:ContentTabItem runat="server"> <Template> <ig:WebDataGrid ID="DlgSelectedItemsWDG" runat="server" Height="98%" Width="99%" > </ig:WebDataGrid> </Template> </ig:ContentTabItem> <ig:ContentTabItem runat="server"> <Template> <ig:WebDataGrid ID="DlgSurplusItemsWDG" runat="server" Height="98%" Width="99%"> </ig:WebDataGrid> </Template> </ig:ContentTabItem> </Tabs></ig:WebTab>
Hi bernhardus,
I could not reproduce this, and without being able to reproduce this our developers were not able to offer much insight on what would cause this. I would like to perform a remote session with you to see if I can help resolve it that way.
I have created support case #CAS-134326-F9Z8H0 to discuss this more in private with you. You can find the support case with further details here:
https://ko.infragistics.com/my-account/support-activity
Thank you for your investigation.
Could you reproduce the behaviour? I have some screenshots I can upload if needed.
Yesterday a user mentioned that the other grid in the dialog showed the same behaviour. Meanwhile I put a button on the page. The user can click this button, a javascript function will make the grid visible then and the grid behaves as expected.
Hi Bernhardus,
After discussing this issue with my supervisor, I am following up with our developers for some more insight on this issue.
I am currently discussing this with our engineers and I will have more information for you by Monday.
If you have any further questions or concerns with this issue, please let me know.
I am currently looking into reproducing this with the information you have provided. I will need a little more time to get my sample together.
I will have another update for you by Wednesday. If you have any further questions or concerns with this, please let me know.