Hello,

First of all thank you for the good explain. Yet I have not tested this problem, but I'm sure that it is as described above. This evantually will happen in Chrome.

You are right the – form is just in the DOM and it seems that it has a focus, which causes this.

I will correct the problem

Thank you very much

Best Regards

Tony

Hello,

I'm not sure, but this maybe should be addressed to the creators of this plugin (Maybe they say the same – that you should address the problem here)

Also short – I never worked with struts2, so I can not help. Try to see what options in the grid are diffrent from those set in the struts2 plugin. Maybe you will look here

Forum

where the autoencode by default is false, but in this plugin is set to true.

Not sure if this will help a lot, but..

Best Regards

Tony

Thanks Lynn,

We are always listening and trying to improve.

Best Regards

Tony

Hello,

Thanks.

Did you try the script?

Also I know that using eval is not safe.

I will see if we can done it better. Thank you for the link – it help me to understand another way of doing this and maybe we will change this behaviour.

Best Regards

Tony

Hello,

Try to use triggerToolbar with setTimeout.

Best Regards

Tony

Hello,

Thanks.

Seems reasonable, but if you close the page at another moment maybe another error will apper.

For now this will stay so.

Anyway thank you very much for this.

Best Regards

Tony

Hello

Klaus, Thank you for the good explanation.

Short this is a bug

Hello,

Forgot to say that the setGridwidth should be set on both

Try this

loadComplete: function ()