You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Per Newgro <pe...@gmx.ch> on 2014/04/29 15:44:02 UTC
How can i avoid that urls in src attributes are handled by wicket?
Hi *,
we have a page which contains markup like this
...
<script type="text/x-handlebars" id="template">
<img src="{{ url }}" alt="{{ name }}" />
</script>
...
After rendering the page the markup looks like this
<script type="text/x-handlebars" id="template">
<img src="../{{ url }}" alt="{{ name }}" />
</script>
Please note the ../ before the {{ url }}
Until now i thought that wicket handles only markup within html tags containing a wicket:id.
But it seems that "Wicket gone wild" here :-).
So my question would be: How can i avoid that wicket handles the src attribute in "non-wicket" markup?
Thanks for your support
Per
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: How can i avoid that urls in src attributes are handled by wicket?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
https://issues.apache.org/jira/browse/WICKET-5288
On Tue, Apr 29, 2014 at 3:49 PM, Ernesto Reinaldo Barreiro <
reiern70@gmail.com> wrote:
> There was a patch a few releases ago that made wicket scan inside <script>
> tags for for components. Try putting the body inside a CDATA section.
>
>
> On Tue, Apr 29, 2014 at 3:44 PM, Per Newgro <pe...@gmx.ch> wrote:
>
>> Hi *,
>>
>> we have a page which contains markup like this
>>
>> ...
>> <script type="text/x-handlebars" id="template">
>> <img src="{{ url }}" alt="{{ name }}" />
>> </script>
>> ...
>>
>> After rendering the page the markup looks like this
>> <script type="text/x-handlebars" id="template">
>> <img src="../{{ url }}" alt="{{ name }}" />
>> </script>
>>
>> Please note the ../ before the {{ url }}
>>
>> Until now i thought that wicket handles only markup within html tags
>> containing a wicket:id.
>> But it seems that "Wicket gone wild" here :-).
>>
>> So my question would be: How can i avoid that wicket handles the src
>> attribute in "non-wicket" markup?
>>
>> Thanks for your support
>> Per
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>
--
Regards - Ernesto Reinaldo Barreiro
Re: How can i avoid that urls in src attributes are handled by wicket?
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
There was a patch a few releases ago that made wicket scan inside <script>
tags for for components. Try putting the body inside a CDATA section.
On Tue, Apr 29, 2014 at 3:44 PM, Per Newgro <pe...@gmx.ch> wrote:
> Hi *,
>
> we have a page which contains markup like this
>
> ...
> <script type="text/x-handlebars" id="template">
> <img src="{{ url }}" alt="{{ name }}" />
> </script>
> ...
>
> After rendering the page the markup looks like this
> <script type="text/x-handlebars" id="template">
> <img src="../{{ url }}" alt="{{ name }}" />
> </script>
>
> Please note the ../ before the {{ url }}
>
> Until now i thought that wicket handles only markup within html tags
> containing a wicket:id.
> But it seems that "Wicket gone wild" here :-).
>
> So my question would be: How can i avoid that wicket handles the src
> attribute in "non-wicket" markup?
>
> Thanks for your support
> Per
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro