Hi,
We have a page with RadDock that contains custom DockCommands. The custom commands are created dynamically on server-side.
Works great. That is, with Q2.
Today I realized that images are not rendered for the custom commands in Q3. Instead, it shows the default expand/collapse arrow (see attached image). Otherwise, the commands work well.
The html generated for Q2 looks like that:
and the html for Q3
The custom images are in the css class (a.dockCommandEdit, a.dockCommandDelete) and the hover images are in the respective hover classes.
The documentation for RadDock mentions only changes in custom RadDock skins that are not backward compatible.
Is that a known issue?
eyal
We have a page with RadDock that contains custom DockCommands. The custom commands are created dynamically on server-side.
Works great. That is, with Q2.
Today I realized that images are not rendered for the custom commands in Q3. Instead, it shows the default expand/collapse arrow (see attached image). Otherwise, the commands work well.
The html generated for Q2 looks like that:
<span class="rdCommands"> |
<a class="rdCollapse" title="Collapse"></a> |
<a class="dockCommandDelete" title="Poista"></a> |
<a class="dockCommandEdit" title="Muokkaa"></a> |
</span> |
and the html for Q3
<ul class="rdCommands"> |
<li><a title="Muokkaa"><span class="dockCommandEdit"> </span></a></li> |
<li><a title="Poista"><span class="dockCommandDelete"> </span></a></li> |
<li><a title="Collapse"><span class="rdCollapse"> </span></a></li> |
</ul> |
The custom images are in the css class (a.dockCommandEdit, a.dockCommandDelete) and the hover images are in the respective hover classes.
The documentation for RadDock mentions only changes in custom RadDock skins that are not backward compatible.
Is that a known issue?
eyal