4 ms·
I don't understand what you're saying. Firstly, web apps can never see anything after a # in a URL: the browser does not send it to them. Javascript can see it,
by seldo 17y ago
I don't understand what you're saying. Firstly, web apps can never see anything after a # in a URL: the browser does not send it to them. Javascript can see it, but I don't think that's what you meant.
With progressive enhancement, your URLs should look like http://www.example.com/products/bungee-cords http://www.example.com/products/bungee-cords. If clicked they should render the page as appropriate. JavaScript, if enabled, will attach a handler to the links and when it sees you trying to click on /products/bungee-cords will halt that click and instead make an AJAX request for the equivalent content. There should be no need to have # links whatsoever.
- boucher 17y agoThat ignores the fact that people want the URL field to reflect the current state of things, so that URLs can be copied out and pasted elsewhere. It also ignores the fact that there is no way to set the URL field (through JavaScript or any other mechanism) without actually triggering a page change.