Named links (anchors) broken by RTE
|Reported by:||moogle||Owned by:|
|Component:||Administration||Keywords:||RTE needs-patch anchors|
A named link has two parts:
1) <a name="jump"></a>
2) <a href="#jump">
Because most posts are viewed from many paths (ie: www.site.com/, www.site.com/2006/, and www.site.com/category/postsname/) relative paths are easiest to use. It is difficult and inefficient to hardcode an absolute path while writing a post that will work in all instances without a full page reload. The current best-case for hardcoded paths is to get the post-slug while editing, and build all the #2's based on that. When anyone clicks on that absolute path from the front-page or archives the browser will redirect them to the hardcoded path.
Can the WYSIWG editor be made to recognize the "#" symbol in a link and not "correct" those links to an absolute path?
Change History (11)
- Cc moogle added
- Keywords bg|reporter-feedback added; bg|needs-patch removed
comment:7 @foolswisdom — 9 years ago
- Keywords RTE needs-patch added; bg|reporter-feedback WYSIWG bg|2nd-opinion bg|has-patch removed
comment:8 @foolswisdom — 9 years ago
- Keywords anchors added
- Summary changed from Named links broken by WYSIWG editor to Named links (anchors) broken by RTE