Hello SandorD,
I'm going to have to disagree, if you check the following example you will note that the icon is registered in a <style> tag and theoretically should be handled like all the previous style hacks we performed. I think the problem now is that the PartialExtRenderer is trying to place it in the head of the page which obviously doesn't exist due to the separation from MVC.
Example.aspx:
<%@ Page Language="C#" Inherits="System.Web.Mvc.ViewPage" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head id="Head1" runat="server">
<title>Example</title>
</head>
<body>
<ext:ResourceManager ID="ResourceManager1" runat="server" />
<ext:Label ID="Label1" runat="server" Icon="Accept" Text="Accept" />
</body>
</html>
Generates the following:
<style type="text/css">
.icon-accept{background-image:url(/icons/accept-png/ext.axd) !important;}
</style>
Vladsch, I would think that since we have hijacked the life cycle of controls and how they render for MVC having a clause for the icons to not be rendered in the head of the site but rather the same method as all <style> tags in a partial would be the best solution. Your thoughts?
I'm hoping I don't have to register icons in the master or parent page ... if so fml.
Cheers,
Timothy
Posting Permissions
| Frameworks and Tools for .NET Developers