Theme broken in Firefox/Mozilla browsers in Solaris OS

[Neel Haldar, módosítva 15 év-val korábban]

I have observed that Liferay presents a different link layout when the OS is
Solaris (both in Mozilla 1.7 and Firefox). The most notable thing is that the
drop down menu under "Welcome". It appears in a straight line instead of
a drop down. (see the image in the URL below)

http://support.liferay.com/browse/LEP-5995

The userAgent of this Mozilla/Firefox browser is in Solaris OS is ...

User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20070606

However, when I change the UserAgent string of this browser to the String
that IE presents, everything works fine in the same Mozilla/Firfox browser
in Solaris.

Is it because the jquery browser detection script is unable to find Solaris
in its list ? I tried modifying the j2browse.js by adding a line like following ...
(I have very limited jquery knowledge)

solaris: /SunOS/.test(pl),

but that did not help.

Can someone please tell me how to make sure we have support for browsers
running in Solaris ? Any pointer will be appreciated.

Thanks
-Neel

[JR Houn, módosítva 15 év-val korábban]

Thread moved: Custom Theme Development.

Hi Neel-
Thanks for raising up this issue and the LEP ticket. I'm going to go ahead and see what is being done to include other setups in the browser sniffing mechanism that helps display javascript.
-jr

[Nate Cavanaugh, módosítva 15 év-val korábban]

Hi Neel,
Thanks so much for posting this and filing an error report. This is why open source is so great.

I went ahead and tested it out with your user agent, and it seems that our script is indeed broken. However, I did a bit of research, and it seems like your Firefox is reporting the wrong User Agent as well. From what I could see, the Firefox UA should be something like this:

Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20061228 Firefox/2.0.0.1
(notice the Firefox/version at the end).

And this is confirmed all the way back to when it was Firebird, so that should be listed.

However, our script should be able to fail gracefully, and there is an error in there. I'll commit the fix to trunk, and upload the file to the support ticket as well.

Thanks for your help Neel,