Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <20093822.1159993400576.JavaMail.root@brutus>
Date: Wed, 4 Oct 2006 13:23:20 -0700 (PDT)
From: "Jeff Bischoff (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Commented: (TOMAHAWK-713) Auto Scroll silently fails on Core
 1.1.4 and Tomahawk nightly
In-Reply-To: <5486550.1159370930139.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/TOMAHAWK-713?page=comments#action_12439958 ] 
            
Jeff Bischoff commented on TOMAHAWK-713:
----------------------------------------

Wendy, I'm not entirely sure. Perhaps I'm mistaken about the reason for the javascript changes. 

Regardless, a quick look at the generated source for just about any example page reveals dramatically different javascript between Tomahawk 1.1.3 and Tomahawk 1.1.5 (nightly). There are new functions, like "oamSetHiddenInput" and "oamSubmitForm." These were not present in earlier versions. There seems to be some sort of javascript disconnect between Tomahawk 1.1.5 and Core 1.1.4 that affects autoscrolling.

I think Martin would know about this stuff?

> Auto Scroll silently fails on Core 1.1.4 and Tomahawk nightly
> -------------------------------------------------------------
>
>                 Key: TOMAHAWK-713
>                 URL: http://issues.apache.org/jira/browse/TOMAHAWK-713
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>    Affects Versions: 1.1.5-SNAPSHOT
>         Environment: MyFaces Core 1.1.4 and Tomahawk nightlies (dated 2006-09-26 or 2006-09-27)
> Tested in Firefox and Internet Explorer browsers
>            Reporter: Jeff Bischoff
>         Attachments: simple.war
>
>
> When using MyFaces Core 1.1.4 and the latest Tomahawk nightlies (dated 2006-09-26 or 2006-09-27), the Auto Scroll functionality fails. There is no error message in the application logs nor in javascript console. This is presumably related to the javascript changes made to ensure compatibility with the RI. This is a major bug, since latest Tomahawk should be compatible with the Core 1.1.4 release.
> This breakage can be observed simply by taking the latest tomahawk-examples nightly download, and substituting in the Core 1.1.4 jars. I will attach such an example.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira