Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix scroll restoration #256

Merged
merged 1 commit into from
Apr 30, 2021
Merged

Conversation

PaperStrike
Copy link
Member

@PaperStrike PaperStrike commented Apr 27, 2021

PR Checklist

  • The commit message follows guidelines for NexT.
  • Tests for the changes was maked (for bug fixes / features).
    • Muse | Mist have been tested.
    • Pisces | Gemini have been tested.
  • Docs in NexT website have been added / updated (for features).

PR Type

  • Bugfix.
  • Feature.
  • Code style update (formatting, local variables).
  • Refactoring (no functional changes, no api changes).
  • Documentation.
  • Translation.
  • Other... Please describe:

What is the current behavior?

See #74.

Issue resolved:

What is the new behavior?

See next-theme/pjax#4.

  • Link to demo site with this changes:
  • Screenshots with this changes:

How to use?

In NexT _config.yml:

@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.469% when pulling aa3b2fb on PaperStrike:scroll-reload into 17bd19d on next-theme:master.

@PaperStrike PaperStrike marked this pull request as draft April 27, 2021 15:39
@PaperStrike PaperStrike marked this pull request as ready for review April 29, 2021 12:51
@PaperStrike PaperStrike added this to the 8.4.0 milestone Apr 29, 2021
@stevenjoezhang stevenjoezhang merged commit c2c1d82 into next-theme:master Apr 30, 2021
@PaperStrike PaperStrike deleted the scroll-reload branch June 1, 2021 05:51
lingyf pushed a commit to lingyf/hexo-theme-next that referenced this pull request Jan 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants