You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by "helena (JIRA)" <ji...@apache.org> on 2005/12/13 06:37:46 UTC

[jira] Updated: (FOR-763) forrest css cross-browser handling of inheritance

     [ http://issues.apache.org/jira/browse/FOR-763?page=all ]

helena updated FOR-763:
-----------------------

    Description: 
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.

  was:
There appears to be a difference between the handling of css inheritance on Internet Explorer versus Mozilla  Firefox.
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.


> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira