Hi Cristi

On Sun, Apr 6, 2008 at 3:09 PM, Cristi Toth <[EMAIL PROTECTED]> wrote:
> Hi,
>
> The issue TRINIDAD-1042 duplicates TRINIDAD-799 (which is not assigned to
> skinning, but to components)

Ah, okay, thanks.  I only scanned the skinning issues - didn't see 799.

> Andrew originally had these ideas:
>
> Possible implementations:
>
> 1) @agent ie6 { ... }
>
> 2) @agent ie { @agentVersion 6 { ... } }

I prefer #1 over #2 - #1 seems more natural to me.

> A more general and more powerful approach would be to allow developers to
> use a regex on the browser version:
>
> @agent match /MSIE [67]/

This is clearly more flexible, whereas something like #1 or #2 is
simpler/easier to use (no need to be familiar with regexp, or with the
format of agent strings).   Since #1 would be sufficient to allow us
to port our existing version-dependent XSS styles to CSS, I would
prefer that we implement this approach, and consider the question of
whether we require more flexible regexp-based matches as a separate
enhancement request.

> I could at least handle this issue, but we have to agree on one format
>  and one other short question: should we also support version for platforms?

I don't see a strong reason to add this, though if people have use
cases where this is necessary we can certainly consider it.

Andy

Reply via email to