Posted by chandrabhan on December 18, 2008 at 2:56pm
Jump to:
| Project: | Read More Link (Drupal 6 and earlier) |
| Version: | 6.x-5.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Todd Nienkerk |
| Status: | closed (won't fix) |
Issue Summary
In many a sites I have seen that when "read more" link is clicked, the page automatically scrolls to the text of the post immediately after the teaser text within the full post view. It is, as if, you are continuing reading from where you have left of in the teaser view.
Will it possible to implement that?
Comments
#1
I'd be interested in this also. Or even if a new page is displayed, it should be displayed with the top of the page situated at the end of the teaser text. Right now when anyone clicks on "read more" link it takes them to the top of the posting, and people have to start reading from the start again to find the point where they left off.
#2
Hmm. This would require adding an anchor to the node at the teaser split. Interesting idea, though it could be difficult to implement.
#3
I think we would need to patch node.module to add an anchor at the
<!--break-->tag. Something like:This is the last line of the teaser.
<a id="read_more" name="read_more"></a>
This is the first line after the teaser.
#4
I added this as a feature request to Drupal 7.x: #429528: Add an anchor tag in place of the break tag when viewing full node
#5
I'll mark this as postponed for 7.x
#6
No new features are being added to Drupal 7.x, so this feature request falls applies to this module. Marking active and re-filing as a 6.x-5.x-dev issue.
This will require some input filter work. See #624224: Add anchor to take user directly to unread content for more info.
#7
Subscribe. I'd love to see this too.
#8
I've looked into this extensively and have concluded that the
<!--break-->tag is so deeply embedded in core behavior that an anchor cannot be added without (1) hacking core or (2) adding complicated, hackish behavior to this module.This may be easier to do in Drupal 7.x, which uses a completely different workflow for rendering nodes. I'm marking this as "won't fix." A new issue may be opened for the Drupal 7.x branch later.