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

markdown h1 header render error on windows and macos #7120

Closed
5 of 6 tasks
frank-lam opened this issue Apr 6, 2022 · 1 comment
Closed
5 of 6 tasks

markdown h1 header render error on windows and macos #7120

frank-lam opened this issue Apr 6, 2022 · 1 comment
Labels
bug An error in the Docusaurus core causing instability or issues with its execution closed: duplicate This issue or pull request already exists in another issue or pull request

Comments

@frank-lam
Copy link

frank-lam commented Apr 6, 2022

Have you read the Contributing Guidelines on issues?

Prerequisites

  • I'm using the latest version of Docusaurus.
  • I have tried the npm run clear or yarn clear command.
  • I have tried creating a repro with https://new.docusaurus.io.
  • I have read the console error message carefully (if applicable).

Description

When I compile the same Markdown file locally on two different systems, Windows and MacOS, I get two different effects.

Macos uses the first level title in Markdown as the title of the current document, but Windows displays both.

Personally, I think the preview method in MacOS is better.

Hopefully, officials can fix this problem by adding configuration, so as to avoid the preview differences between different systems.

macos

image
image

windows

image
image

Reproducible demo

No response

Steps to reproduce

NA

Expected behavior

NA

Actual behavior

NA

Your environment

{
"name": "notes.frankfeekr.cn",
"version": "0.0.1",
"private": true,
"scripts": {
"docusaurus": "docusaurus",
"start": "docusaurus start",
"build": "docusaurus build",
"swizzle": "docusaurus swizzle",
"deploy": "docusaurus deploy",
"clear": "docusaurus clear",
"serve": "docusaurus serve",
"write-translations": "docusaurus write-translations",
"write-heading-ids": "docusaurus write-heading-ids"
},
"dependencies": {
"@docusaurus/core": "^2.0.0-beta.18",
"@docusaurus/preset-classic": "^2.0.0-beta.18",
"@easyops-cn/docusaurus-search-local": "0.23.0",
"@mdx-js/react": "^1.6.22",
"clsx": "^1.1.1",
"plugin-image-zoom": "^1.1.0",
"prism-react-renderer": "^1.3.1",
"react": "^17.0.1",
"react-dom": "^17.0.1"
},
"browserslist": {
"production": [
">0.5%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}

Self-service

  • I'd be willing to fix this bug myself.
@frank-lam frank-lam added bug An error in the Docusaurus core causing instability or issues with its execution status: needs triage This issue has not been triaged by maintainers labels Apr 6, 2022
@Josh-Cena
Copy link
Collaborator

Josh-Cena commented Apr 6, 2022

Duplicate of #7044

@Josh-Cena Josh-Cena added closed: duplicate This issue or pull request already exists in another issue or pull request and removed status: needs triage This issue has not been triaged by maintainers labels Apr 6, 2022
@Josh-Cena Josh-Cena marked this as a duplicate of #7044 Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error in the Docusaurus core causing instability or issues with its execution closed: duplicate This issue or pull request already exists in another issue or pull request
Projects
None yet
Development

No branches or pull requests

2 participants