Of course, this could render
<link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" /> (as stated)
but i've seen (for instance in this very site)
<link rel="shortcut icon" href="/jira/images/icons/favicon.ico"> (type is missing)
<link rel="icon" type="image/png" href="/jira/images/icons/favicon.png"> (different type and rel)
Given those alternatives, perhaps we can take care of this in a more generic way.
Perhaps the favicon parameter should only generate:
<link rel="shortcut icon" href="/jira/images/icons/favicon.ico">
and we can have an additional parameter 'links' which will accept a List or Collection or array of a
new class, named Link or HtmlLink or HtmlRelation. This should have href, media, name, rev, rel, title, type
properties and will be able to render them if they contain a non-null value.
See http://www.blooberry.com/indexdot/html/tagpages/l/link.htm for more, but i think these are the most important
and they do cover css inclusion in a much better way than the currently supported.
Returning to the favicon issue, I also believe that the favicon parameter (ot whatever its name will be) should be an IAsset but also a simple string.