myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Bischoff (JIRA)" <>
Subject [jira] Commented: (TOMAHAWK-713) Auto Scroll silently fails on Core 1.1.4 and Tomahawk nightly
Date Tue, 10 Oct 2006 17:24:20 GMT
    [ ] 
Jeff Bischoff commented on TOMAHAWK-713:

I am doing all testing for this bug using the Tomahawk examples application (both modified
and unmodified versions).

There is no sign of any dummyForm code on the generated page.

There is one form around everything inside the f:view. In the unmodified example, the form
has no id which generates a warning when viewed. I have modified versions where I gave the
form an id - there is no error then, but the broken behaviour remains. In both cases, all
commandLinks are nested within the form.

You're not able to reproduce this problem?

> Auto Scroll silently fails on Core 1.1.4 and Tomahawk nightly
> -------------------------------------------------------------
>                 Key: TOMAHAWK-713
>                 URL:
>             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, simple2.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:
For more information on JIRA, see:


View raw message