I may reconsider it.
--
Kevin
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 17, 2008 2:34 PM
To: Tapestry users
Subject: Re: T5: CSS Injection and IE Conditional Comments
I think these comments are right on the money.
Perhaps it would be easi
I think these comments are right on the money.
Perhaps it would be easier if expansions were allowed inside comments?
That's entirely doable.
On Feb 15, 2008 11:55 AM, Robert Zeigler <[EMAIL PROTECTED]> wrote:
> Expansions won't work (directly) for the asset, b/c expansions inside
> of comments
Ahh, good to know. It's nothing I've ever tried, but I just assumed would
work. In that case, I'd go with Robert's suggestions (since they'll
actually work).
--
Kevin
On 2/15/08 2:55 PM, "Robert Zeigler" <[EMAIL PROTECTED]> wrote:
> Expansions won't work (directly) for the asset, b/c expansi
Expansions won't work (directly) for the asset, b/c expansions inside
of comments are ignored, so trying to do something like:
Isn't going to work.
What you /could/ do is to have the entire comment generated in java
code, and then have all of the comment spit out as an expanded string
in
You could just use an expansion in your template for the asset. Not quite
the same, but it would accomplish the same goal.
--
Kevin
On 2/15/08 12:28 PM, "lebenski" <[EMAIL PROTECTED]> wrote:
>
> Hi guys,
>
> Does anyone know of a mechanism of utilizing IE Conditional Comments for
> importin
Hi guys,
Does anyone know of a mechanism of utilizing IE Conditional Comments for
importing browser-specific CSS, but using the standard tapestry method of
css injection via the page class, i.e. something like:
private PageRenderSupport _pageRenderSupport;
@Inject
@Path("$path/t
