Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 39406 invoked from network); 16 Dec 2006 15:53:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Dec 2006 15:53:19 -0000 Received: (qmail 62692 invoked by uid 500); 16 Dec 2006 15:53:25 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 62617 invoked by uid 500); 16 Dec 2006 15:53:24 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 62606 invoked by uid 99); 16 Dec 2006 15:53:24 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO [127.0.0.1]) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Dec 2006 07:53:24 -0800 Message-ID: <458416B0.6000207@apache.org> Date: Sat, 16 Dec 2006 16:54:24 +0100 From: Carsten Ziegeler User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Issues 1811 and 1916 still open References: <003a01c71f67$d8d02280$6500a8c0@RBE4> <45824A51.4040301@apache.org> In-Reply-To: <45824A51.4040301@apache.org> X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Carsten Ziegeler wrote: > Rob Berens wrote: >> The issues 1811 ([PATCH] Flow Script: Allow dynamic loading of JavaScript objects even when scope is locked) and >> 1916 (viewData in event handlers sometime undefined) >> are still open. >> Could someone please have a look before releasing 2.1.10. >> > I have not enough knowledge about 1811 - so perhaps someone else can > have a look at it? > The same with 1916 (it's a bug I hit myself several times); so far the > code looks fine to me. Rob, did you try with latest from svn again? > If someone could solve this bug it would really be great! > Ok, I fixed 1916 by always setting viewData (either to the value or null). This should not cause any problems. Carsten -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/