On Feb 16, 1:17 pm, Vyacheslav Akhmechet <[email protected]> wrote:
> > How is this going to mix with AJAX updates? > > For the updates to show up on the query string, the relevant links and > forms would have to be AJAX-free (at least until someone works on > integrating the URL hash thing into weblocks). I just noticed how Google Code handles this: it has straight base URIs http://code.google.com/p/PROJECT/source/browse/ and then appends widget configuration in a simple manner after the hash sign: http://code.google.com/p/PROJECT/source/browse/#svn/tags We should adopt this. It allows us to have basic bookmarkability among JS users, a good fallback for those without JS and still works with AJAX requests. It's still abuse of the fragment identifier but W3C doesn't offer alternatives right now, unfortunately. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
