Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 22488 invoked from network); 28 Nov 2005 15:52:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Nov 2005 15:52:42 -0000 Received: (qmail 77957 invoked by uid 500); 28 Nov 2005 15:52:38 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 77913 invoked by uid 500); 28 Nov 2005 15:52:38 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 77896 invoked by uid 99); 28 Nov 2005 15:52:37 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Nov 2005 07:52:37 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mkienenb@gmail.com designates 64.233.162.200 as permitted sender) Received: from [64.233.162.200] (HELO zproxy.gmail.com) (64.233.162.200) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Nov 2005 07:54:06 -0800 Received: by zproxy.gmail.com with SMTP id i11so1035936nzi for ; Mon, 28 Nov 2005 07:52:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GANxShtQ0mie+9IioBb2THNkmza+iSdcYOJbkUHtHgSGszfr+DuCEjtL25ra/UoJHq+2y/FQpMnpqdKjB40BktuPl7m4fef/NI/xFYw6qPw5UXnVZwWI5sDTrDt/3WLXf3K7qlgc3gwDOpqYxJIKFeVWI5DQeHBjCzAtHyERc+E= Received: by 10.36.108.14 with SMTP id g14mr3429254nzc; Mon, 28 Nov 2005 07:52:14 -0800 (PST) Received: by 10.37.22.11 with HTTP; Mon, 28 Nov 2005 07:52:14 -0800 (PST) Message-ID: <8f985b960511280752p6931758nabc7b7a52e3d08a9@mail.gmail.com> Date: Mon, 28 Nov 2005 10:52:14 -0500 From: Mike Kienenberger To: MyFaces Discussion Subject: Re: Redisplay a JSF site after submit with the scrolling state previously used? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8f985b960511280725t10b95b1dy72f30684899383f7@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N It's not a component -- it's just a configuration option:

org.apache.myfaces.AUTO_SCROLL

true

If true, a javascript function will be rendered that is able to restore the former vertical scroll on every request. Convenient feature if you have pages with long lists and you do not want the browser page to always jump to the top if you trigger a link or button action that stays on the same p= age. Default: "false" Your best bet is to do a view source and look at function getScrolling() and how it's called from each UICommand. On 11/28/05, Matthias Kahlau wrote: > Hi! > > > Is there a separate component which supports autoscrolling to the compone= nt > which submitted the form? I can't find one in the Tomahawk TLD Doc. > > > Regards, > Matthias > > > -----Urspr=FCngliche Nachricht----- > > Von: users-return-12945-mkahlau=3Dweb.de@myfaces.apache.org > > [mailto:users-return-12945-mkahlau=3Dweb.de@myfaces.apache.org]Im Auftr= ag > > von Mike Kienenberger > > Gesendet: Montag, 28. November 2005 16:26 > > An: MyFaces Discussion > > Betreff: Re: Redisplay a JSF site after submit with the scrolling state > > previously used? > > > > > > Matthias, > > > > There's already javascript support in MyFaces for doing "autoscrolling.= " > > > > Currently, it always scrolls back to the UICommand component that > > submitted the form. > > > > I've tried to write my own javascript that scrolls it to any arbitrary > > component on the page, but I don't really know javascript. > > > > It'd be great if you could figure out how to take advantage of the > > existing autoscroll javascript to make it work with arbitrary > > components. Maybe we could then figure out a tag to set the > > autoscroller -- or something like that :) > > > > On 11/26/05, Matthias Kahlau wrote: > > > Hi! > > > > > > > > > I use a method for valueChangeListeners of selectOneMenu and other mu= lti > > > choice tags. In the valueChangeListeners method, I can set the state = of > > > boolean variables, which are used in the JSF site in attributes like > > > disabled and rendered of some tags. > > > > > > A valueChangeListener method is invoked when the value of the > > related tag > > > changes, which causes a submit of the form. The problem is, > > that some tags > > > are below the fold, and when the form is submitted because of a > > value change > > > and then redisplayed again, the site is scrolled to top, and > > the user has to > > > scroll down to the component, where he changed the value. > > > > > > Does somebody know if it is possible to redisplay the site with the > > > scrolling state previoulsy used? (I know that I could > > alternatively set the > > > disabled and rendered states of the tags by using client-side > > JavaScript, > > > without submitting the form and changing the scrolling state, but tha= t's > > > more work and doesn't use the server-side facilities). > > > > > > > > > Regards, > > > Matthias > > > > > > > >