Re: Is it a bug where the uri has not changed, but the back button must be activated more than once?

> Is it a bug where the uri has not changed, but the back button must be
> activated more than once?
> or to put it another way, what events does the back button register, when
> the page has not changed?
> how can one build an ajax app in svg and be certain that one hit of the back
> button will return the user to the site before they visited the ajax web
> app?
> not the usual issue around being able to navigate within the ajax app. [?]

Overall this seems a matter apparently more fit to the SVG-developers
group [1]. ;-)

Sorry but the text is a bit confuse (at least, to me). Could you
perhaps explain a bit more clearly: when you mean pressing the back
button, do you mean navigating to a previous state of (the same)
document or navigating to a previous (but different) document?

If you are referring to navigate within document states (within the
same document), then I'm not sure if it's possible at all. An HTML
(not SVG related) framework I'm aware of, qooxdoo [2], includes
support for this using neat tricks - you may perform back/forward
navigation withing AJAX widgets (try the showcase [3], for instance).
This seems to be implemented using fake HTML anchors (for example, Maybe it's possible to
develop a similar technique in SVG, but this will require further
investigation and interoperability tests for current

If you refer to pressing the back button to navigate to the previous
document, this already seems to happen in most UA as far as I know.
Batik Squiggle implements it (with SVG document support only) and
browsers which natively implement SVG seem to properly allow pressing
the back/forward buttons to previous/subsequent (HTML/SVG) documents.
Browser plug-ins (such as ASV for Internet Explorer) also seem to
behave more or less as expected.

SVG already includes a mechanism to navigate within SVG content and/or
SVG views [4], although AFAIK implementation support is low (any at
all?). I believe that SVG 1.2 addresses this matter in a more precise
way so let's wait to see what future will bring. :-)

Hope this helps,

 Helder Magalh„es


Received on Thursday, 26 June 2008 10:15:38 UTC