ISSUE-88 - Public View

AJAX (and serious use of javascript in general) b0rks history, bookmarks, etc

State:
CLOSED
Product:
All
Raised by:
Charles Mccathienevile
Opened on:
2006-09-21
Description:
Manipulating the DOM to update pages generally means that it is impossible to 
bookmark them, retrieve them in history, link to them, etc, in any but their 
initial state.

This is a problem in common with frames and sites that hide everything by 
pushing all interaction via POST requests. Although Ajax generally provides 
much better services, we are also breaking one of the main features of the web 
- that if I see something cool, I can send someone else there.

I suspect that we should look at two approaches - one trying to provide 
guidance to authors (I know that Dave R's JS-heavy slide system does solve this 
problem - perhaps he could be convinced to write more generally on how to deal 
with this issue), and the other to talk to user agent developers about what can 
be done in this regard.

(Raising this issue completes ACTION-208)

Note: Some of these links may be accessible only to W3C Members.

Related emails:
  1. ISSUE-88: AJAX (and serious use of javascript in general) b0rks history, bookmarks, etc (from dean+cgi@w3.org on 2006-09-21)
  2. ISSUE-88: AJAX (and serious use of javascript in general) b0rks history, bookmarks, etc (from dean+cgi@w3.org on 2006-09-21)
  3. Re: ISSUE-88: AJAX (and serious use of javascript in general) b0rks history, bookmarks, etc (from dsr@w3.org on 2006-10-02)

Related notes:

2006-09-21: Sigh. I doubled this up because sometimes I am dumb :(