[x] The changes have been tested (for bug fixes / features).
[ ] Docs in NexT website have been added / updated (for features).
PR Type
[x] Bugfix.
[ ] Feature.
[ ] Improvement.
[ ] Code style update (formatting, linting).
[ ] Refactoring (no functional changes).
[ ] Documentation.
[ ] Translation.
[ ] Other... Please describe:
What is the current behavior?
Issue resolved:
If we use utterances or giscus comment system with pjax enabled, and use 'og:title' to map blog post with issue or discussion, then the comment does not load correctly if we change to another page. The reason is that utterance/giscus will consult <meta property="og:title" content="***"> in the head, which is not reloaded by pjax. The the comment shown is actually comments for the last page.
What is the new behavior?
The meta tag for 'og:title' is reloaded by pjax, and comments are load correctly.
PR Checklist
PR Type
What is the current behavior?
Issue resolved:
If we use utterances or giscus comment system with pjax enabled, and use 'og:title' to map blog post with issue or discussion, then the comment does not load correctly if we change to another page. The reason is that utterance/giscus will consult
<meta property="og:title" content="***">
in the head, which is not reloaded by pjax. The the comment shown is actually comments for the last page.What is the new behavior?
The meta tag for 'og:title' is reloaded by pjax, and comments are load correctly.