In the "ice:outputStyle" taglib documentation it indicates that the filename contained
in the 'href="file.css"' parameter will also attempt to deliver a browser-specific version of the CSS file
if the browser-specific file is found, and the "file.css" if not.

Icefaces uses the User-Agent header in the request to determine what browser-specific CSS file to deliver.

Browser-specific CSS files look like "file_ie7.css" or "file_ie8.css".

The way this delivery is accomplished in the original code is by appending a new "link" tag to the existing one, so there are then
two links seen in the source, one for the original file and one for the new browser-specific (e.g. "..._ie8.css") one.

In the example application we have two CSS files, and each of their browser-specific counterparts existing in the "css" directory:

css/test1.css
css/test1_ie7.css
css/test1_ie8.css
css/test2.css
css/test2_ie7.css
css/test2_ie8.css

When "ice:outputStyle" tags are provided for both css/test1.css and css/test2.css, we should see four <link> tags like this:

<link href="css/test1.css" rel="stylesheet" type="text/css" />
<link href="css/test1_ie8.css" rel="stylesheet" title="_ie8" type="text/css" />
<link href="css/test2.css" rel="stylesheet" type="text/css" />
<link href="css/test2_ie8.css" rel="stylesheet" title="_ie8" type="text/css" />

Unfortunately, sometimes this doesn't work.

In particular, if an absolute path starting with "/" is used in the "href" attribute, or if a relative path starting with ".."
is used, IceFaces OutputStyleRenderer code looks in the wrong place to determine if the browser-specific version of
the file exists.