myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafa PĂ©rez" <raja...@gmail.com>
Subject Re: [TRINIDAD] Skinning for different agents
Date Fri, 17 Oct 2008 06:36:15 GMT
Maybe there is a bug in the documentation at
http://myfaces.apache.org/trinidad/devguide/skinning.html ??

In the section named 'Skining CSS Features' we can see:

         /* for ie 5 and 6, we also need some margins.*/
        @agent ie (version: 5) and (version: 6)
        {
          af|someComponent {margin: 5px;}
        }

By the way, some of the navigation links of the site are broken again:

* Skinning Selectors
(http://myfaces.apache.org/trinidad/trinidad-api/skin-selectors.html)
* Developer Guide
(http://myfaces.apache.org/trinidad/trinidad-api/devguide/index.html)
* Plugins (http://myfaces.apache.org/trinidad/trinidad-api/plugins/index.html)
* Trinidad 1.2.x
(http://myfaces.apache.org/trinidad/trinidad-api/trinidad-1_2/index.html)

Regards,

-- Rafa




On Thu, Oct 16, 2008 at 11:05 PM, Andrew Robinson
<andrew.rw.robinson@gmail.com> wrote:
> You are forgetting the "and" after the browser type
>
> see here for the correct syntax:
>
> https://issues.apache.org/jira/browse/TRINIDAD-799
>
> Instead of:
> @agent ie (version: 7) and (version: 8){
>
> use:
> @agent ie and (version: 7) and (version: 8){
>
> basically the syntax is:
>
> @agent [restriction] (and [restriction])*
>
> Where "ie" is a restriction and "(version: #)" is a restriction. I
> believe the agent name has to be first though (I am not sure that
> "@agent (version: 6) and ie" would work)
>
> -Andrew
>
> On Thu, Oct 16, 2008 at 11:56 AM, Amaris Nieves <daraii.tech@gmail.com> wrote:
>> I have the following lines in my skin css:
>>
>> @agent ie (version: 5) and (version: 6){
>> .....
>> }
>> @agent gecko,mozilla, webkit{
>>  .....
>> }
>>
>> @agent ie (version: 7) and (version: 8){
>>  .....
>> }
>>
>> All of them works well except the last one. I've also tried with @agent ie
>> (version: 7) only but it still doesn't work.
>>
>> What can be the problem?
>>
>

Mime
View raw message