When reading the article, click on the title of the sidebar can not jump. [solved]

[ChungZH]

I agree and want to create new issue

• Yes, I was on Hexo Docs page, especially on Templates, Variables, Helpers and Troubleshooting.
• Yes, I was on NexT Documentation Site.
• And yes, I already searched for current issues and this is not help to me.

---

Expected behavior

Click on the title of the sidebar to jump to the title.

Actual behavior

When reading the article, click on the title of the sidebar can not jump.

Steps to reproduce the behavior

1. N/A
2. N/A
3. N/A

• Link to demo site with this issue: N/A
• Link(s) to source code or any usefull link(s): N/A

Node.js and NPM Information

v8.10.0
6.3.0

Package dependencies Information

Hexo Information

Hexo version

hexo: 3.7.1
hexo-cli: 1.1.0
os: Windows_NT 10.0.17730 win32 x64
http_parser: 2.7.0
node: 8.10.0
v8: 6.2.414.50
uv: 1.19.1
zlib: 1.2.11
ares: 1.10.1-DEV
modules: 57
nghttp2: 1.25.0
openssl: 1.0.2n
icu: 60.1
unicode: 10.0
cldr: 32.0
tz: 2017c

Hexo Configuration

# Hexo Configuration
## Docs: https://hexo.io/docs/configuration.html
## Source: https://github.com/hexojs/hexo/

# Site
title: ChungZH's blog
subtitle: 萌新之站~
description: ChungZH的博客 | ChungZH's Blog
keywords:
author: ChungZH
language: zh-CN
timezone: Asia/Shanghai

# URL
## If your site is put in a subdirectory, set url as 'http://yoursite.com/child' and root as '/child/'
url: http://chungzh.cn
root: /
permalink: :title/
permalink_defaults:

# Directory
source_dir: source
public_dir: public
tag_dir: tags
archive_dir: archives
category_dir: categories
code_dir: downloads/code
i18n_dir: :lang
skip_render:

# Writing
new_post_name: :title.md # File name of new posts
default_layout: post
titlecase: false # Transform title into titlecase
external_link: true # Open external links in new tab
filename_case: 0
render_drafts: false
post_asset_folder: false
relative_link: false
future: true
highlight:
  enable: true
  line_number: true
  auto_detect: false
  tab_replace:
  
# Home page setting
# path: Root path for your blogs index page. (default = '')
# per_page: Posts displayed per page. (0 = disable pagination)
# order_by: Posts order. (Order by date descending by default)
index_generator:
  path: ''
  per_page: 10
  order_by: -date
  
# Category & Tag
default_category: uncategorized
category_map:
tag_map:

# Date / Time format
## Hexo uses Moment.js to parse and display date
## You can customize the date format as defined in
## http://momentjs.com/docs/#/displaying/format/
date_format: YYYY-MM-DD
time_format: HH:mm:ss

# Pagination
## Set per_page to 0 to disable pagination
per_page: 10
pagination_dir: page

# Extensions
## Plugins: https://hexo.io/plugins/
## Themes: https://hexo.io/themes/
theme: next-rr

# Deployment
## Docs: https://hexo.io/docs/deployment.html
deploy:
  type: git
  repo: 
    coding: [email protected]:ChungZH/ChungZH_blog.git,master


feed:
  type: atom
  path: atom.xml
  limit: 20
  hub:
  content:
  content_limit: 140
  content_limit_delim: ' '

search:
  path: search.xml
  field: all
  format: html
  limit: 10000


baidusitemap:
  path: baidusitemap.xml
sitemap:
  path: sitemap.xml

markdown:
  render:
    html: true
    xhtmlOut: false
    breaks: false
    linkify: true
    typographer: true
    quotes: '“”‘’'
  plugins:
    - markdown-it-footnote
    - markdown-it-sup
    - markdown-it-sub
    - markdown-it-abbr
    - markdown-it-emoji


symbols_count_time:
  symbols: true
  time: true
  total_symbols: true
  total_time: true

NexT Information

NexT Version:

• Latest Master branch
• Latest Release version
• Old version

NexT Scheme:

• All schemes
• Muse
• Mist
• Pisces
• Gemini

NexT Configuration:

Other Information

[sli1989]

Maybe caused by hexo-renderer-markdown-it plugin (related issues). Can you change the markdown render to reproduce this problem?

[ChungZH]

But how do use emoji?

[sli1989]

So you want use hexo-renderer-markdown-it to realize emoji? perhaps u need to try other plugins like hexo-filter-github-emojis?

[ChungZH]

Thx.

[ChungZH]

Thx.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.