Eric,
The ability to provide additional CSS files for specific browsers is
meant to simplify your life not make it hell - sorry about that. First
look at the global sitemap.xmap at the root of the webapp around line
136 you should find something like the following:
<map:selector name="browser"
src="org.apache.cocoon.selection.BrowserSelector"
logger="sitemap.selector.browser">
<browser name="explorer" useragent="MSIE"/>
<browser name="explorer6" useragent="MSIE 6"/>
<browser name="explorer7" useragent="MSIE 7"/>
<browser name="safari2" useragent="(KHTML, like Gecko) Safari"/>
<browser name="safari3" useragent="(KHTML, like Gecko) Version/3"/>
<browser name="firefox" useragent="Firefox"/>
<browser name="firefox1" useragent="Firefox/1."/>
<browser name="firefox2" useragent="Firefox/2."/>
</map:selector>
These are the definitions that your theme is using to select
stylesheets, basically if it sees the string in the useragent field
then the request is tagged. A request can have multiple tags, so if
the useragent string contains MSIE 7 it will match the tags "explorer"
and "explorer7"
I hope that light on the mechanism makes things simpler.
Scott--
On Feb 10, 2009, at 2:37 PM, Eric Luhrs wrote:
> Hi all,
> After looking at this problem for a few days, I feel like I'm going
> nuts. Hopefully someone on this list can help me with it.
>
> My Login page sometimes pulls the wrong CSS for IE. All other pages
> pull the right CSS for different versions of IE, and Firefox works
> fine no mater what page is requested.
>
> Here's where things get strange.... Sometimes IE6 pulls the
> stylesheet for IE7. Other times IE7 pulls the stylesheet for IE6.
> As far as I can tell, it seems to depend on which version of IE is
> the first to view the login page after tomcat has been rebooted. So
> if I reboot tomcat and then visit the Login page with IE6,
> subsequent visits with IE7 will continue to pull the CSS for IE6.
> If I reboot tomcat again, and then visit the Login page with IE7,
> subsequent visits with IE6 will continue to pull the CSS for IE7.
> Doesn't seem to matter if I visit with Firefox first, it's only the
> first version of IE that gets stuck. If I disable caching in Cocoon
> the problem goes away, but then "advanced search" gives a Null
> Pointer Exception (see posting from a few days ago for details on
> this).
>
> I'm using 1.5.2 code that is a few weeks old. My theme is based
> heavily on Reference, with a few changes to the XSL. I also
> modified the EPerson sitemap.xmap file to make the "login" link skip
> the Login Chooser and go directly to /ldap-login. I don't think
> this is causing the problem though, because the same thing happens
> when I use the standard EPerson sitemap.
>
> Does this make sense to anyone? All suggestions will be GREATLY
> appriciated!
>
> Eric
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills
> and code to
> build responsive, highly engaging applications that combine the
> power of local
> resources and data with the reach of the web. Download the Adobe AIR
> SDK and
> Ajax docs to start building applications
> today-http://p.sf.net/sfu/adobe-com_______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
