> Thorsten Scherler commented on FOR-763:
> ---------------------------------------
> 
>  Is this still an open issue (like stated from Ross and David skins are 
> slowly dying)?

Please don't associate with individual people.
Decisions about project direction are made by
the community.

Is there a "css inheritance" issue with a dispatcher-enabled
site? If not, then please add a comment to say so.

> Will resolve (wont fix) it after a week from now.
> 
> lazy consensus active.

I think that the issue should remain open. Someone might
need to continue with skins for a while, i.e. all those
people who went against our advice and developed their
own skins.
http://forrest.apache.org/docs/skins.html#introduction

If one of those people wants to fix this open issue
then they can.

-David
> 
> 
> > forrest css cross-browser handling of inheritance
> > -------------------------------------------------
> >
> >          Key: FOR-763
> >          URL: http://issues.apache.org/jira/browse/FOR-763
> >      Project: Forrest
> >         Type: Bug
> >   Components: Skins (general issues)
> >     Versions: 0.7
> >  Environment: browsers: IE, Mozilla Firefox, no others tested
> >     Reporter: helena
> >     Priority: Trivial
> 
> >
> > There appears to be a difference between the handling of css inheritance on 
> > Internet Explorer versus Mozilla  Firefox. Tigris was being used however 
> > there is nothing wrong with tigris, it simply does not handle all browsers 
> > and could be added to by someone all knowing on client -side dev.
> > Easily solved by making css more specific where necessary.
> > Worth a QA if app  end user client  unknown. This was a significant UI bug 
> > on one of my live sites.
> > Luckily caught within a few hours of latest build but by a user. eek. Added 
> > Firefox to my debugging routine.