You should at least escape your ':', i.e. something like: BODY
WICKET\:MESSAGE * { }
But I doubt it will work on any browser. If you really want to keep the
wicket:message tags (imho you're better of without them), you could wrap
them in another container (div/span) and use that conatiner as a cs
I know I can work around this, it is just I see it as a place to improve
framework.
I want to use immediate-child selectors because I see benefits from this
whatever that is
I know that in runtime those tags goes away but while working with raw html
files (let say graphic designer takes them and f
1) Why do you use immediate-child selectors (involving > ) instead of just
child selectors (without the >)? The selector ".custom-component-class header"
will work.
2) wicket namespace tags are removed in deployment mode (or if you tell markup
settings to strip them), so wicket:child will disapp
Then I don't really know. Perhaps file a bug report with Microsoft ;-)
Frank
On Sat, May 17, 2008 at 12:47 PM, John Krasnay <[EMAIL PROTECTED]> wrote:
> On Sat, May 17, 2008 at 09:57:13AM +0200, Frank Bille wrote:
>> What happens if you add the wicket namespace to the html tag?
>>
>> http://wick
On Sat, May 17, 2008 at 09:57:13AM +0200, Frank Bille wrote:
> What happens if you add the wicket namespace to the html tag?
>
> http://wicket.apache.org";>
>
> Frank
>
I thought about that, but the page already has the declaration.
jk
> On Fri, May 16, 2008 at 7:33 PM, John Krasnay <[EMAIL P
What happens if you add the wicket namespace to the html tag?
http://wicket.apache.org";>
Frank
On Fri, May 16, 2008 at 7:33 PM, John Krasnay <[EMAIL PROTECTED]> wrote:
> I've just noticed a specific problem with Wicket tags interfering with
> IE6. I have a page that uses the jqModal plugin for
Yeah, that's the easy fix I mentioned, and it indeed fixes the problem.
jk
On Fri, May 16, 2008 at 01:43:07PM -0400, Ryan Gravener wrote:
> You can place
> getMarkupSettings().setStripWicketTags(true); into your Application.init().
> I believe these are automatically stripped when you are in depl
You can place
getMarkupSettings().setStripWicketTags(true); into your Application.init().
I believe these are automatically stripped when you are in deployment mode.
On Fri, May 16, 2008 at 1:33 PM, John Krasnay <[EMAIL PROTECTED]> wrote:
> I've just noticed a specific problem with Wicket tags in