Earlier this month, there was a thread [1] about the "component not
found" problem. I can't reply as I wasn't subscribed yet.
[1]
http://old.nabble.com/component-xxx:yyy:zzz-not-found-on-page-td27080437.html
I had the same problem recently, and after banging my head against the
wall for a wh
Thomas, as someone who frequently likes trying "really dumb things" -- I
appreciate you giving a heads up on this issue. I was likely going to run
into this at some point anyway ;)
On Wed, Jan 27, 2010 at 3:46 AM, Thomas Kappler
wrote:
> Earlier this month, there was a thread [1] about the "compo
Thomas,
Thanks for this. I may also have run into the multiple page load you say this
might cause. Can you confirm if this is the case for any appreciate you giving a heads up on this issue. I was likely going to run
> into this at some point anyway ;)
>
> On Wed, Jan 27, 2010 at 3:46 AM, Thoma
On 01/27/10 21:51, Steve Swinsburg wrote:
Thomas,
Thanks for this. I may also have run into the multiple page load you
say this might cause. Can you confirm if this is the case for any
I can confirm it happens for any , with Firefox 3.5.
An without source is not valid HTML, so I'd try to avoi
You could file enhancement request to make
EmptySrcAttributeCheckFilter also report images whose src starts with
#.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.a
On 01/28/10 09:35, Marat Radchenko wrote:
You could file enhancement request to make
EmptySrcAttributeCheckFilter also report images whose src starts with
#.
Cool, I didn't even know about this filter. Its javadoc nicely explains
the issue.
I filed WICKET-2709 to make it check for src="#", t
