Last Updated: 17 Nov 2017 11:36 by ADMIN
A workaround is to remove the loading sign functionality by placing the following script at the end of the form tag

The second override is necessary only if you use the OnClientDataLoaded event to alter the data and add fields in the data object that do not exist in the server response. You need to rename the OnClientDataLoaded method call to use your actual method name.

You can find an example of both workarounds and their usage attached.

Some additional information:
- If possible, move the tiles out of the AJAX request, as this will eliminate all of the problems. Depending on the actual scenario perhaps you can make sure they are not in an update panel (e.g., position them absolutely on the page while keeping their markup out of the partial postback).
- consider moving any data formatting logic from the event handler to the template. You can define functions that format the code in the template, not only in the event. An example is available in the attached file. Alternatively, you can return the data formatted from the web service.
- consider reducing the time interval for the requests, because after the AJAX request, only 1 of 2 requests will update the tile UI.
Last Updated: 13 Nov 2015 09:11 by ADMIN
Possible workarounds:
- switch to the Classic RenderMode of the TileList: http://docs.telerik.com/devtools/aspnet-ajax/controls/tilelist/mobile-support/render-modes
- disable DragAndDrop: http://docs.telerik.com/devtools/aspnet-ajax/controls/tilelist/functionality/drag-and-drop
Last Updated: 14 Feb 2014 11:55 by ADMIN
A possible workaround is to override the CSS for tiles that need no selection abilities:
	<telerik:RadContentTemplateTile runat="server" ID="RadContentTemplateTile1" EnableSelection="false" CssClass="noSelection">

	.noSelection div.rtileSelectedIcon
		display: none;
		border: 2px solid transparent;
Last Updated: 18 Oct 2013 10:03 by ADMIN
Sometimes the OnClientClicked event is fired ony after the second tap, the first shows the peek template. Sometimes this can also be observed with the NavigateUrl. It is easiest seen when JS code is executed from the NavigateUrl, e.g.:  NavigateUrl="javascript:CDRequestMenu()"
This is related to the fact that there are no separate events on a touch device for mouseover, mousedown, click and mouseup.