Try Now
More in this section

Forums / Suggestions / Shrinking the markup possible?

Shrinking the markup possible?

2 posts, 0 answered
  1. Steve
    Steve avatar
    3037 posts
    03 Dec 2008
    12 May 2011
    Link to this post
    Every ID is obnoxious in the backend and frontend with browse\edit enabled

    I realize its mostly asp.nets retarded AutoID, but like...
    <span id="Content_ctl00_ctl00_ctl00_sidebar_ctl07_ctl00_ctl07_ctl00_buttonText">Last <strong>5 years</strong></span>
    Is that nessesary?

    or this
    <span id="Content_ctl00_ctl00_ctl00_lockWindow_ctl00_ctl02_buttonText">Cancel</span>

    I mean there's no CSS class assigned to either of these so why do they even need IDs over the wrapping anchors?  If it's a custom control couldn't it just render the span with the text directly?
  2. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    01 Feb 2016
    16 May 2011
    Link to this post
    Hello Steve,

    By default we use the Predictable ClientID mode which was introduced with ASP.NET 4.0. However the longer ids which you are seeing in places in the backend are because those controls have their naming container explicitly set to use AutoID. The need for this arises from the fact that we have moved Sitefinity 4.0 from .NET 3.5 to 4.0. There was a huge overhead for some backend controls, because in order to use the new naming convention they had to be rewritten. Unfortunately at the moment there isn't much that can be done to improve the IDs of those controls.

    All the best,
    Radoslav Georgiev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
2 posts, 0 answered