It is stripped because you won't be able to find any wicket: tags in
any of the HTML standards. Browsers won't be able to do anything with
the tag. At best they'll leave it alone, but browsers playing with the
wicket tags can also wreck havoc when doing dom manipulations.

Martijn

On Tue, Sep 9, 2008 at 11:41 PM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> wicket:message is stripped from the final markup in development mode,
> this is intentional.
>
> Martijn
> On Tue, Sep 9, 2008 at 11:31 PM, insom <[EMAIL PROTECTED]> wrote:
>>
>> I'm not sure if this is a Wicket bug or my own misunderstanding of
>> development vs. deployment modes. My markup included the following:
>>
>> <wicket:message style="display: inline; background-color: yellow;
>> font-weight: bold;" key="takeTheTest">Take the Test</wicket:message>
>>
>> That worked find in development mode, but when I switched to deployment, the
>> style attribute was stripped from the final source. In the end I solved it
>> like this:
>>
>> <wicket:message key="takeTheTest">Take the Test</wicket:message>
>>
>> Is that intentional different in development/deployment, and if so, why?
>> --
>> View this message in context: 
>> http://www.nabble.com/Development-Deployment-style-attributes-tp19401772p19401772.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to