Could you perhaps isolate the problem into the smallest reproducible scenario
and share this sample code (form definition / flowscript / jxtemplate).
Which version of Cocoon are you using by the way?
Robby
From: Patricia Déchandol [mailto:pdechan...@ajlsm.com]
Sent: Tuesday, March 13, 2012
Of course it can. But to get an answer to that question I advise you to check
the known bugs list of chrome itself. Did you already inspect the generated
(x)html using chrome developer or firebug? Maybe you can spot any obvious
mistake?
Robby
From: Patricia Déchandol
Possible encoding issue?
From: Patricia Déchandol [mailto:pdechan...@ajlsm.com]
Sent: Tuesday, March 13, 2012 1:28 PM
To: users@cocoon.apache.org
Subject: Re: Problem with Cocoon Forms continuation in Google Chrome
Making tests, the error appears or not on different servers on which the same
The Problem you reported seems to me as if it was a HTTP posting issue in
connection with the submitid of the widget which caused the submit.
You should use Chrome/Safari Web Tools to trace the HTTP network traffic
to see if there is a submitid request parameter passed and if it differs
from
