[ http://issues.apache.org/jira/browse/TOMAHAWK-713?page=comments#action_12439970 ] Jeff Bischoff commented on TOMAHAWK-713: ----------------------------------------
Wendy, thanks for looking into this. Can't believe I didn't notice that "autoscroll.jsf" page! I was just randomly testing on the other pages. The problem is still there, but you've narrowed it down a bit. When I go to autoscroll.jsf, it behaves as expected (it down not scroll back to the top). *However*, those are all h:commandLink. If I change the source to contain a t:commandLink instead, autoscroll breaks on that page (The browser scrolls to the top of the page, when I click on any link). I tried it also with t:commandButton, and this fails to autoscroll also. This leads to two conclusions: * The mere presence of tomahawk 1.1.5 jar does not interfere with the correct autoscrolling of Core components. * When tomahawk 1.1.5 is used on top of Core 1.1.4, autoscrolling is broken for t:commandButton, t:commandLink, and any components that rely on t:commandLink (e.g. datascroller). >From looking at the generated javascript, there is definately a new submission >mechanism being used by these components. That's where the new "oam" >javascript functions come into play... > 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
