Yea, I recently went in a similar route in T4... see
https://svn.apache.org/repos/asf/tapestry/tapestry4/trunk/tapestry-framework/src/java/org/apache/tapestry/html/Style.jwc
and specifically the parameter "ieCondition"
On Thu, Oct 22, 2009 at 10:03 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
> Actually, what I'd like to do is open up the API defined by
> RenderSupport to make it easy to specify that a CSS file is for IE.
> It could generate the necessary comment around the the script tag for
> you. Perhaps include an additional annotation for including JavaScript
> resources with the necessary qualifier (or, perhaps because this is a
> rare case, leave the annotation alone, but include the API change).
>
> On Thu, Oct 22, 2009 at 11:50 AM, cordenier christophe
> <christophe.corden...@gmail.com> wrote:
>> Well i know my Post was about a detail, but generally even if the problem is
>> really Minor (in our case to allow IE hacks :), I think it make sense to fix
>> it, especially when the fix is obvious.
>>
>> But, I will follow your advise and develop a LeComment component...
>>
>>
>> Christophe.
>>
>>
>> 2009/10/22 Andreas Andreou <andy...@di.uoa.gr>
>>
>>> In fact the comment string shouldn't contain -- at all
>>> as per the specs... it makes browsers think the comment has ended
>>>
>>> Anyway, i guess you could write a custom component IeComment to handle this
>>> and add an improvement request in JIRA if you think the Comment class
>>> should be
>>> changed
>>>
>>> On Thu, Oct 22, 2009 at 7:14 PM, cordenier christophe
>>> <christophe.corden...@gmail.com> wrote:
>>> > Hello
>>> >
>>> > We are going into a strange bug with IE :) and hack like <!--[if ...-->
>>> >
>>> > These hacks seems to be not interpreted because Tapestry automatically
>>> add a
>>> > space character between '<!--' and '['
>>> >
>>> > Here is the implementation of Comment class :
>>> >
>>> > �...@override
>>> > void toMarkup(Document document, PrintWriter writer, Map<String,
>>> String>
>>> > namespaceURIToPrefix)
>>> > {
>>> > writer.print("<!-- ");
>>> > writer.print(comment);
>>> > writer.print(" -->");
>>> > }
>>> >
>>> > Actually, it is not required to have space characters but specification
>>> does
>>> > not allow a comment ending in --->. The following example is
>>> *not*well-formed.
>>> >
>>> > http://www.w3.org/TR/xml/#sec-comments
>>> >
>>> > What should be done here ?
>>> >
>>> > Please do not tell me not to use IE :)
>>> >
>>> > Regards,
>>> > Christophe.
>>> >
>>>
>>>
>>>
>>> --
>>> Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr
>>> Tapestry / Tacos developer
>>> Open Source / JEE Consulting
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>>
>>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
