![Known Issues and Limitations ASP.NET 12.1 1.png](images/Known_Issues_and_Limitations_ASP.NET_12.1_1.png)
The following table summarizes the known issues and limitations of the Ultimate UI for ASP.NET® 2013.1 release. Detailed explanations and possible workarounds are provided for some of the issues follow the summary table.
- Workaround available
- No known workaround
- Fix planned
When using the Designer in Microsoft® Visual Studio with WebHierarchicalDataGrid and WebHierarchicalDataSource inside an UpdatePanel, there may be an issue with the Designer continuously repainting and appearing as if it is frozen.
Workaround
When a WebTab , with either no width defined or width defined as a percentage, is placed in a <TD>
element with no width defined, occasionally the WebTab control is unable to calculate the tab width correctly and, as a result, display the tab excessively wide.
Workaround
When using the WebDataGrid control with active Input Method Editor (IME) mode with Edit mode configured to trigger on key press, the first character entered by the user may display as a Roman character.
This issue can occur because when interpreting the IME, the browser requires an actual INPUT
element. Because the WebDataGrid / WebHierarchicalDataGrid displays data in <TD>
elements as opposed to INPUT`s, the browser will use Roman characters until the `INPUT
is displayed for editing, which is the point at which the IME can accept component characters or processing commands. This results in an initial Roman character as the first input character followed by the correct component characters.
Workaround
In JavaScript:
function entered(grid, args) {
var editor = args.getEditor();
setTimeout(function () { editor.set_value("") }, 0);
}
With WebDataGrid and WebTab controls inside an UpdatePanel, asynchronous post-backs could cause a memory leak.
This issue appears to originate in the browser or the ASP.NET AJAX library as it is also reproducible with Microsoft’s GridView and an HTML table within the UpdatePanel.
Workaround
In the WebSchedule control, recurring appointments render incorrectly when they span over multiple days including a weekend.
Workaround
In C#:
WebSchedule.DetailEventCalenderWebScheduleInfo.EnableMultiDayEventBanner = false;
The following topics provide additional information related to this topic.