[Seaside] Any design pattern for scroll issue when using call/answer?

Hilaire Fernandes hilaire at ofset.org
Tue Mar 24 13:31:25 UTC 2009


Are there a well known pattern for seaside to deal with the browser
scrolled page when using sub-component and callback?

When using a lot sub-components, each time the work-flow returns, the
browser scrolls back to the top of the html canvas.

Once Randall suggested Anchor. I am not sure how it can be generalized
for  lot of sub-components
Lukkas explains about how to do it with two components:

In the other hand, is it possible to generalize the use of the
scriptaculous inPlaceEdit for any component?

Or may be just keep the html canvas to reside in one screen height when
there is user editing taking place?

Thanks for any additional tips.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message
	=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20090324/9d4a01ec/attachment.pgp

More information about the seaside mailing list