Tres Seaver wrote:
Note that the fragment identifier is *never* going to be passed to the
server by a "real" browser: instead, the browser strips of the fragment
part, submits the remainder of the URL to the server, and then does a
search for the appropriate '' element *on the client side*.
I'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> Hi,
>
> I've got a situation where a form submit will eventually end up in an
> action that does (in Zope 2):
>
> context.REQUEST.RESPONSE.redirect('/path/to/foo/#bar')
>
> This works fine through the web, but using zope.t
