Return-Path: 
 <dev-return-99274-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 4652 invoked from network); 24 Apr 2008 00:52:06 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 24 Apr 2008 00:52:06 -0000
Received: (qmail 41492 invoked by uid 500); 24 Apr 2008 00:52:07 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 41104 invoked by uid 500); 24 Apr 2008 00:52:06 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 41093 invoked by uid 99); 24 Apr 2008 00:52:06 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 17:52:06 -0700
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [63.231.195.113] (HELO mpls-qmqp-02.inet.qwest.net)
 (63.231.195.113)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2008 00:51:20 +0000
Received: from mpls-pop-02.inet.qwest.net (mpls-pop-02.inet.qwest.net
 [63.231.195.2])
	by mpls-qmqp-02.inet.qwest.net (Postfix) with QMQP id F3EC253BD15
	for <dev@cocoon.apache.org>; Thu, 24 Apr 2008 00:51:32 +0000 (UTC)
Received: from unknown (HELO ?192.168.0.70?) (63.225.106.48)
  by mpls-pop-02.inet.qwest.net with SMTP; 24 Apr 2008 00:51:32 -0000
Message-ID: <480FD994.2050004@apache.org>
Date: Wed, 23 Apr 2008 18:51:32 -0600
From: Jason Johnston <jjohnston@apache.org>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Question about cocoon vs. IE setting
References: <422D410BD61FC04185076AD99AA7207A03162024@inilmx01.lgmt.trdo>
In-Reply-To: <422D410BD61FC04185076AD99AA7207A03162024@inilmx01.lgmt.trdo>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi Yiwen, good to talk to you again!

(For future reference, user questions like this are better suited for 
the users@cocoon.apache.org mailing list.)

The bug you're encountering is not a Cocoon-specific issue, but rather a 
problem with how IE handles <button/> elements.  If you have multiple 
buttons on a page, IE will submit the name=value parameters for *all* of 
them, not just the one you clicked.  This is obviously a problem when 
your server-side code expects just name=value pair.

The "safe" solution is, as Jeroen suggested, to use <input 
type="submit"/> instead of <button/>, and that is in fact what is 
created by the default CForms styling XSLT.  However, there are 
advantages to <button/>, namely that it can display complex content as 
its label whereas <input/> can only display a simple text label.

Now, since I happen to have inside knowledge of the project you're 
working on ;-), I do know that displaying complex labels is required, so 
using <input/> isn't really an option.  That's why your product's custom 
CForms styling XSLT overrides the default template to create <button/>s 
instead.  To get around the IE bug, there is a client-side script that 
listens for button clicks, and performs some DOM manipulation to 
obfuscate the names of the non-clicked buttons so that they don't send 
clashing request parameters.  It sounds to me like this client-side 
script has somehow been broken, or is not working properly under a 
specific circumstance.

I hope that helps; if not, feel free to email me directly since there's 
no reason to bug the fine folks on this list with non-Cocoon discussions.

--Jason



Xu, Yiwen wrote:
> We are currently experiencing a problem for button submission for IE 
> browser. We tested it in several IE. it worked successfully in 
> successfully, but some other IE seems unable to get the submitted button 
> id which cause our application failure (see below for more details). All 
> IE we originally tested was version 6. We upgrade those problematic IE 
> to 7 and 8.1, but same problem still occurred. Can anyone tell me what 
> IE configuration or OS configuration might impact this cocoon button 
> submission process?
>  
> Thanks in advance !!!
>  
> ----- Details ----------
> This is the html code which contains the "Summit" button.
> <button title="" value="1" name="msag-query-QueryAction" 
> id="msag-query-QueryAction" type="submit" class="submit">Submit</button>
>  
> This is the debug message in the javascript program which loads and 
> processes the form:
>     cocoon.log.error("submitted button ID : " + form.submitId + "\n 
> submitted widget :" + form.getWidget().getSubmitWidget());
>  
> For those IE which doesn't have problem, the debug result shows:
> 
>     submitted button ID : msag-query-QueryAction  submitted widget 
> :Submit-msag-query-QueryAction
> 
>  
> 
> But for those problematic IE, the debug result is:
> 
>     submitted button ID : undefined 
> 
> submitted widget :Submit-msag-query-QueryAction
> 
> which caused cocoon throws  " java.lang.IllegalStateException: 
> SubmitWidget can only be set once. "
>