Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of agallardo@agssa.net designates
 165.98.153.184 as permitted sender)
Message-ID: <439E22E9.6070707@agssa.net>
Date: Mon, 12 Dec 2005 19:24:57 -0600
From: Antonio Gallardo <agallardo@agssa.net>
Organization: AG Software, S. A.
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: RFC: Ajax Roadmap
References: <609B1C73-907D-47B3-9E11-8E507DDEA863@apache.org>
 <439E1AD1.9050005@apache.org>
In-Reply-To: <439E1AD1.9050005@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (ags01.agssa.net: 10.0.0.7 is whitelisted)
 receiver=ags01.agssa.net; client-ip=10.0.0.7; helo=[10.0.0.7];
 envelope-from=agallardo@agssa.net;
 x-software=spfmilter 0.93 http://www.acme.com/software/spfmilter/;

Carsten Ziegeler wrote:

>I think this global switch is a misconception. Can we change the meaning
>to: "use ajax if it's enabled in the form *and* if the current browser
>supports it?" Currently I only have the choice for switching ajax on for
>*all* users. Now if they happen to have turned off javascript, they
>simply can't use the form.
>So I would prefer to have a detection mechanism, if the current browser
>supports ajax or something like that.
>  
>
AFAIK, we have a detection mechanism at the browser level:

http://svn.apache.org/viewcvs.cgi/cocoon/blocks/forms/trunk/java/org/apache/cocoon/forms/resources/js/cforms.js?view=markup

(see the end of the "cocoon.forms.submitForm", at the end we founda 
comment: "/// Non ajax-aware browser : regular submit"/
/
Best Regards,

Antonio Gallardo.

/

>Apart from that a general +1 for your ideas.
>
>Carsten
>  
>