Hi all,
in my application I register a custom ISerializer implementation in the
WebApplication.init() method as follows:
@Override
protected void init() {
super.init();
getFrameworkSettings().setSerializer(new
MySerializer(getApplicationKey()));
...
This works
only for textfields and textareas.
johan, matej says you wanted to track focus for anchors, whats the deal?
-igor
2009/4/16 Peter Gardfjäll peter.gardfj...@gmail.com:
Hi James,
I'm pretty sure that links are part of the problem.
To verify this, try replacing all a tags with e.g. span and see
this Behavior to my parent page
(which other pages extend) and still have the javascript rendered last
in the head?
regards, Peter
2009/4/17 Peter Gardfjäll peter.gardfj...@gmail.com:
Thanks Igor,
the suggested workaround seems to work fine. However, it is not enough
to just override
, James Carman
jcar...@carmanconsulting.com wrote:
Did that code actually work for you? I tried adding this js, but i
couldn't get it to show up in the correct place. And, when I did, it
didn't seem to improve much. Care to share your code?
2009/4/17 Peter Gardfjäll peter.gardfj...@gmail.com
Hi all,
I am working on a wicket application intended to be executed both on
FF3 and IE7.
While working on this application I have discovered that the rendering
of some pages are a lot slower in IE.
The pages that were significantly slower on IE have a couple of things
in common: they are
brains trying to figure this thing out. My page is similar,
a table with lots of cells in them that are links. I've turned off CSS and
other stuff trying to find the bottleneck. I didn't think for a moment that
it might be the links.
James
2009/4/16 Peter Gardfjäll peter.gardfj...@gmail.com
