You cannot do that in an HTML skin because it adds the skinpath to every HREF if the skin gets parsed to ASCX

unless you use this dirty trick:

<a hr<%=""%>ef="<%= NavigateUrl(PortalSettings.HomeTabId) %>">Home</a>

You can use the hack I showed you , which prevents the skin parser from seeing the "href".

Or you can simply edit the ascx skin, but do not forget to remove the HTML skin or you will lose your changes to the ascx if you or someone else accidentally parses the skin.

Yes Sebastian, it would.

But I think this is quite difficult to achieve, without any XHTML issues, or downwards compatibility issues.

We could not  add the skinpath if the path is a full path (http://....) or starting from the root (/.........)

In these cases you can be quite sure the skinner does not want the skinpath added.

In case of inline code it is difficult to be sure what the skinners wants.

You could use <%=somefunction%> for anything... also inside the skinpath folder...

Or we check for a css class "NoParse" for the containing element and not parse it...?
Not sure that is easy to do in the current skin parser..