To everyone who hasn't tried the experiment yet, can you give it a try
now? That would be fabulous. It takes one minute, and it's described
in the e-mail below.
To those have replied already, many thanks.
Does anyone have a theory of the cause yet? I don't, because I still
can't see a pattern.
A summary:
- For most, neither fails. For a few, the first example fails. For a
few others, the second example fails. For one, both failed.
- Proxies don't seem to be the cause, because there is one failure
reported without a proxy.
- Country does not yet seem to be involved, which probably rules out
locales, character sets, and latency.
- Windows is not the cause, because there is one failure with OS X
Leopard.
Cheers,
Geoff
It mostly occurs when a proxy is involved, but there is only one
report of a problem without a proxy. Proxies don' seem to be involved
(although only one failure has been reported
On 17/07/2009, at 10:08 AM, Geoff Callender wrote:
Everyone,
Please try this quick experiment. I am trying to figure out why it
works for some people and not for others.
The experiment is: go to the following two pages and click on "Add a
row"...
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/tables/ajaxformloop1
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/tables/ajaxformlooptailored1
Did it work? Please reply here with whether it worked or not, and
include whether you are running through a proxy, whether you OS is
Windows, and what country you are in.
Hopefully there's a pattern.
Thanks,
Geoff
P.S. The people who reported a problem say that the blackbird
console shows this kind of thing:
# Communication with the server failed: The rendered content did not
include any elements that allow for the positioning of the hidden
form field's element.
# Ajax failure: Status 500 for /jumpstart/examples/tables/
ajaxformlooptailored1
.ajaxformloop
.rowinjector:inject;jsessionid=3BB5CE5E0D166AC91A4561295B8F5151?
t:formcomponentid=examples/tables/
AjaxFormLoopTailored1:personsedit&t:formid=personsedit: The rendered
content did not include any elements that allow for the positioning
of the hidden form field's element.
