Posted by gtaylor on June 26, 2009 at 4:01pm
3 followers
Jump to:
| Project: | Persistent URL |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
The fully qualified URL for a comment includes the anchor. If a user gets an email for this and must login to see it, they lose the anchor context after login. It's there on the login page but disappears after signon.
Will this module fix that?
Comments
#1
Sadly no. The anchor (aka fragment) is not ever sent to the server. The browser keeps that little bit of information to itself. We can't do anything about it, this is simply the way browsers work.
Setting to 'by design', though not my design.
#2
While the fragment is not sent to the server, for URLs constructed with PURL you still have the fragment available.
On outbound, you could copy the fragment as some sort of anchor tag attribute, on inbound you could copy it back as fragment.