You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Hugo Palma (JIRA)" <de...@tapestry.apache.org> on 2007/10/12 11:56:51 UTC
[jira] Created: (TAPESTRY-1818) Template parser should handle CDATA
blocks
Template parser should handle CDATA blocks
------------------------------------------
Key: TAPESTRY-1818
URL: https://issues.apache.org/jira/browse/TAPESTRY-1818
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.5
Reporter: Hugo Palma
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Issue Comment Edited: (TAPESTRY-1818) Template parser should
handle CDATA blocks
Posted by "Chris Lewis (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544469 ]
chrislewis edited comment on TAPESTRY-1818 at 11/21/07 5:56 AM:
-----------------------------------------------------------------
<script> and <style> blocks are declared as having PCDATA in XHTML 1.0 (http://www.w3.org/TR/xhtml1/#h-4.8). I personally view this as broken since characters '<' and '>' are quite important in CSS ans Javascript. Aside from that, it presented me with a problem (currently unsolvable) using T5. I use some 'raw script' to configure some JS behavior, injected into the page body using addScript. In my case I needed to match some elements based on a selector using the prototype method <a href="http://www.prototypejs.org/api/element/getelementsbyselector">getElementsBySelector</a>. In the selector I used the direct child operator ('>'), and after 20-30 minutes of confusion, realized that T5 was filtering this to an entity (for XML correctness).
The problem is that there's no way around this. When the content is declared as having <![CDATA[ ]]>, T5 throws the painful exception:
"Not implemented yet: CDATA[ ... ]"
was (Author: chrislewis):
<script> and <style> blocks are declared as having PCDATA in XHTML 1.0 (http://www.w3.org/TR/xhtml1/#h-4.8). I personally view this as broken since characters '<' and '>' are quite important in CSS ans Javascript. Aside from that, it presented me with a problem (currently unsolvable) using T5. I use some 'raw script' to configure some JS behavior, injected into the page body using addScript. In my case I needed to match some elements based on a selector using the prototype method <a href="http://www.prototypejs.org/api/element/getelementsbyselector">getElementsBySelector</a>. In the selector I used the direct child operator ('>'), and after 20-30 minutes of confusion, realized that T5 was filtering this to an entity (for XML correctness).
The problem is that there's no way around this. When the content is declared as having <b><![CDATA[ ]]></b>, T5 throws the painful exception:
"Not implemented yet: CDATA[ ... ]"
> Template parser should handle CDATA blocks
> ------------------------------------------
>
> Key: TAPESTRY-1818
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1818
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Hugo Palma
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-1818) Template parser should handle
CDATA blocks
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1818:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Template parser should handle CDATA blocks
> ------------------------------------------
>
> Key: TAPESTRY-1818
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1818
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1818) Template parser should handle
CDATA blocks
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554867 ]
Howard M. Lewis Ship commented on TAPESTRY-1818:
------------------------------------------------
The fix for this is part of the fix for TAPESTRY-1600.
You have to be careful to use a <!DOCTYPE> and set the content type for the page to be "text/xml". Only then is the XML Markup Model used, which supports CDATA sections.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
in the template and
@Meta("tapestry.response-content-type=text/xml")
in the Java code.
> Template parser should handle CDATA blocks
> ------------------------------------------
>
> Key: TAPESTRY-1818
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1818
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Hugo Palma
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-1818) Template parser should handle CDATA
blocks
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1818.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.8
> Template parser should handle CDATA blocks
> ------------------------------------------
>
> Key: TAPESTRY-1818
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1818
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.8
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1818) Template parser should handle
CDATA blocks
Posted by "Chris Lewis (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544469 ]
Chris Lewis commented on TAPESTRY-1818:
---------------------------------------
<script> and <style> blocks are declared as having PCDATA in XHTML 1.0 (http://www.w3.org/TR/xhtml1/#h-4.8). I personally view this as broken since characters '<' and '>' are quite important in CSS ans Javascript. Aside from that, it presented me with a problem (currently unsolvable) using T5. I use some 'raw script' to configure some JS behavior, injected into the page body using addScript. In my case I needed to match some elements based on a selector using the prototype method <a href="http://www.prototypejs.org/api/element/getelementsbyselector">getElementsBySelector</a>. In the selector I used the direct child operator ('>'), and after 20-30 minutes of confusion, realized that T5 was filtering this to an entity (for XML correctness).
The problem is that there's no way around this. When the content is declared as having <b><![CDATA[ ]]></b>, T5 throws the painful exception:
"Not implemented yet: CDATA[ ... ]"
> Template parser should handle CDATA blocks
> ------------------------------------------
>
> Key: TAPESTRY-1818
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1818
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Hugo Palma
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Issue Comment Edited: (TAPESTRY-1818) Template parser should
handle CDATA blocks
Posted by "Chris Lewis (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544469 ]
chrislewis edited comment on TAPESTRY-1818 at 11/21/07 5:56 AM:
-----------------------------------------------------------------
<script> and <style> blocks are declared as having PCDATA in XHTML 1.0 (http://www.w3.org/TR/xhtml1/#h-4.8). I personally view this as broken since characters '<' and '>' are quite important in CSS ans Javascript. Aside from that, it presented me with a problem (currently unsolvable) using T5. I use some 'raw script' to configure some JS behavior, injected into the page body using addScript. In my case I needed to match some elements based on a selector using the prototype method getElementsBySelector (http://www.prototypejs.org/api/element/getelementsbyselector). In the selector I used the direct child operator ('>'), and after 20-30 minutes of confusion, realized that T5 was filtering this to an entity (for XML correctness).
The problem is that there's no way around this. When the content is declared as having <![CDATA[ . . . ]]>, T5 throws the painful exception:
"Not implemented yet: CDATA[ ... ]"
was (Author: chrislewis):
<script> and <style> blocks are declared as having PCDATA in XHTML 1.0 (http://www.w3.org/TR/xhtml1/#h-4.8). I personally view this as broken since characters '<' and '>' are quite important in CSS ans Javascript. Aside from that, it presented me with a problem (currently unsolvable) using T5. I use some 'raw script' to configure some JS behavior, injected into the page body using addScript. In my case I needed to match some elements based on a selector using the prototype method <a href="http://www.prototypejs.org/api/element/getelementsbyselector">getElementsBySelector</a>. In the selector I used the direct child operator ('>'), and after 20-30 minutes of confusion, realized that T5 was filtering this to an entity (for XML correctness).
The problem is that there's no way around this. When the content is declared as having <![CDATA[ ]]>, T5 throws the painful exception:
"Not implemented yet: CDATA[ ... ]"
> Template parser should handle CDATA blocks
> ------------------------------------------
>
> Key: TAPESTRY-1818
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1818
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Hugo Palma
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org