[ 
https://issues.apache.org/jira/browse/SHINDIG-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725077#action_12725077
 ] 

lipeng commented on SHINDIG-1103:
---------------------------------

sorry, that is my wrong.
so I can change the code to this, now see it:
<code>
<Content type="html" view="default"> 
    <![CDATA[
    <script>var test='<b>BIG WORDS</b>'</script> 
    <h1>Hello, world!</h1> 
    ]]>
</Content>  
</code>
this is a valid xml structure.
but the bug is still here.

I escape '</b>' to '<\/b>'
the bug be gone.

but this is the correct method?
do we need addslashes for the '/' character in application xml code?

> The bug is that DOMDocument->loadHtml will remove tages like </b> in script.
> ----------------------------------------------------------------------------
>
>                 Key: SHINDIG-1103
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1103
>             Project: Shindig
>          Issue Type: Bug
>          Components: PHP
>    Affects Versions: trunk
>            Reporter: lipeng
>             Fix For: trunk
>
>         Attachments: index-rewriter-test.patch
>
>
> Fixed shindig/php/test/index.php, We can request 
> "http://shindig/test/index.php?test=GadgetRewriterTest"; to get 
> GadgetRewriterTest's result.
> Added shindig/php/test/gadgets/GadgetRewriterTest.php, To test when activate 
> rewriter by rewrite_by_default=true, the rewrite code should change content 
> within the content tag in application xml.
> <code>
> <Content type="html" view="default"> 
>     <script>var test='<b>BIG WORDS</b>'</script>
>     <h1>Hello, world!</h1>
> </Content>
> </code>
> be changed to
> <code>
>     <script>var test='<b>BIG WORDS'</script>
>     <h1>Hello, world!</h1>
> </code>
> The bug is that DOMDocument->loadHtml will remove tages like </b> in script. 
> Every loadHtml calling has that problem. Do you have any solution for this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to