Hi!
Is there a separate component which supports autoscrolling to the component which submitted the form? I can't find one in the Tomahawk TLD Doc. Regards, Matthias > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Auftrag > 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 -- <f:setAutoScrollToHere> or something like that :) > > On 11/26/05, Matthias Kahlau <[EMAIL PROTECTED]> wrote: > > Hi! > > > > > > I use a method for valueChangeListeners of selectOneMenu and other multi > > 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 that's > > more work and doesn't use the server-side facilities). > > > > > > Regards, > > Matthias > > > >
