fwiw - a minor note, but regarding
http://www.ja-sig.org/issues/browse/UP-2428 I just noticed that in:
https://www.ja-sig.org/svn/uPortal/tags/rel-3-2-0-RC1/uportal-war/src/main/webapp/media/skins/universality/uportal3/portal.css
There was the following:
.fl-theme-uportal .fl-tabs li.fl-activeTab,
.fl-theme-uportal .fl-tabs li.fl-activeTab:hover,
.fl-theme-uportal .fl-tabs li.fl-activeTab a,
.fl-theme-uportal .fl-tabs li.fl-activeTab a:hover {background-color:
#fff; border-bottom-color:#fff; color:#508cc9;}
I remember from looking into it back a few months ago when I was working
on MailPortlet that this class (activeTab) was renamed between the
(really) old version of fluid that uPortal was previously using to any
of the newer versions (even in pre v1.0 fluid infusion(?) versions I
think?). I think I remember one of the fluid guys (iirc) saying that
instead of "deprecating" the old class they just renamed it to fit their
naming convention.
I could be wrong though. Just wanted to give you a heads up, and I
apologize in advance if this isn't correct. I was concerned at the time
just because I wasn't sure how many classes changed like that, and that
it might affect the MailPortlet if Fluid were upgraded in uP. I've not
tested MailPortlet with 3.2.0 RC1 or anything other than uP 2.5.3.2 at
the moment, so I can't say for sure whether it affects it at all.
Thanks,
Gary
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
