![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Title:
Cut tags should stay cut (even when on single entry pages)
Area:
entries
Summary:
Currently, the cut tag affects pages that could have more than one entry. I'd like to suggest that cut tags apply to the entry view as well
Description:
Original request (entered as support request #2218):
Is there an html necessary reason why cut tags only work when viewed through a filter?
For example, http://libitina.dreamwidth.org/311800.html (IMO) should take me to a page with a cut tag, and only http://libitina.dreamwidth.org/311800.html#cutid1 should take me to the complete entry.
So, sure, my friendslist is a filter, so it stays nicely uncluttered, but it'd be nice to go to an entry with multiple cut tags and be able to navigate from the 1st one to the 5th one without the gymnastics of finding an easy filter for that page so I can read the text of the cut tags OR remembering the order of the cut tags so I can slip the right number into the URL.
Additional request:
And if you can make this work, I would love for it to be flagged to go upstream for livejournal. Thank you.
<user name="ysobel">'s reply:
Cut tags were originally created so that the content of one entry wouldn't necessarily affect other entries on the page. For example, if someone you subscribe to posts a large image, that will stretch out all of the entries on your reading page, but if they put it behind a cut tag, it won't cause problems.
Because of this, the cut tag affects pages that could have more than one entry. This includes reading pages, your journal page, the tag page if the entry is tagged, and the day page (http://libitina.dreamwidth.org/2009/07/14/). The entry/comment page, because it only has one entry on it, displays the full content.
If you'd like to suggest that cut tags apply to the entry view as well, please see the FAQ referenced above, which describes the process for suggestions.
My response -
Yes, please! I would love this as an improvement.
This suggestion:
Should be implemented as-is.
1 (1.6%)
Should be implemented with changes.
27 (42.2%)
Shouldn't be implemented.
34 (53.1%)
(Other: please comment)
2 (3.1%)