I am dynamically generating my page in code based on options configured and stored in a db. One option is to display a bunch of fields in a modal popup for which I use the WebDialogWindow. I create it in code and add it to a placeholder with a state of hidden and when the page renders all the grids on the page to not display correctly. Baffled by this, I fired up Diff and had a look at the differences in the page source with and without the WebDialogWindow on the page. I discovered that a large list of css classes with names like ig_643f549c_rc11 were not being rendered to the browser, these would happen to be the very classes used to specify the formatting of all the cells (colour, justification etc) in the grids. Has anyone encountered this before? It's very odd indeed! The grid itself renders identically in both cases it's just the missing css classes that cause the issue.
Has anyone found a workaround for this?
Fixes for controls that ship with NetAdvantage for ASP.NET (including any Aikido-based control that are in the RTM product) are shipped in our normal Hotfix cycle. Also, problems that you find in any of the RTM controls (Aikido-base or otherwise) can be reported to our Developer Support team.
Hope that helps.
Devin
Is there any timeline for the issue with WebDialogWindow (Aikido-based controls) to be fixed. I am trying to use the WebDialogWindow on some of my content pages but it is creating problems with the styles of my UltraWebMenu and UltraWebToolbar. I would really like to use the WebDialogWindow in the newest version of our product but cannot sacrifice other controls to use it. It does not seem to override all the styles, it just makes the control backgrounds white with black borders (our menu and toolbar have transparent bg and border)
Please let me know if i can be of any assistance in this.
I believe we actually just identified this issue ourselves internally. It has to do with two different css files we register, one for the classic controls (webgrid) and one for Aikido-based controls (dialog), and as you pointed out the order in which they get rendered.
Since they have the same filename, I beleive its a last in wins scenario in the browser. We are currently trying to identify the best solution to the problem so we can fix it in a hotfix.
I figured it out! It was to do with the order the controls were being added to the page. If I create the tabs containing the grids before I create the modal dialogs it all works ok. Any grid created after has it's css classes supressed for some reason.