Hi,

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):

• ColumnFixing, ColumnMoving, ColumnResizing, Filtering, Sorting, RowSelectors, Selection (with CellSelectType Multiple, CellClickAction Row, ColumnSelectType None, RowSelectType Multiple).
• AutoGenerateColumns is false.

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.

• As far as I know the error does not occur when I open the dialog for the first time after browser or application restart. But maybe I didn't try enough.
• The error occurs erratically after the dialog was opened several times. Several times means a range between 2 or 3 up to 50 or more, using always the same data or different data. After a user had informed me for the first time I tried about 30 minutes until I could reproduce the behaviour.
• We are using Firefox as default browser (release >= 25). Some users have the ability to switch the rendering engine to Internet Explorer inside Firefox. If they do in case of the error then the error does not occure with IE engine (which makes sense since it's like a browser restart), but it occures again when they switch back to Firefox engine. I did not test if the error ever occures when using IE.

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 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.

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.

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.