\r\n \u003Ctitle>\u003C/title>\r\n \u003Cstyle>\r\n /*申明字体*/\r\n @font-face {\r\n font-family: \"iconfont\";\r\n src: url(\"font/iconfont.eot\"); /* IE9*/\r\n src: url(\"font/iconfont.eot?#iefix\") format(\"embedded-opentype\"), /* IE6-IE8 */\r\n url(\"font/iconfont.woff\") format(\"woff\"),\r\n /* chrome、firefox */ url(\"font/iconfont.ttf\") format(\"truetype\"), /* chrome、firefox、opera、Safari, Android, iOS 4.2+*/\r\n url(\"font/iconfont.svg#iconfont\") format(\"svg\"); /* iOS 4.1- */\r\n }\r\n\r\n p {\r\n width: 200px;\r\n border: 1px solid #000;\r\n line-height: 60px;\r\n font-size: 30px;\r\n margin: 100px auto;\r\n text-align: center;\r\n position: relative;\r\n }\r\n\r\n .icon::before {\r\n content: \"\\e628\";\r\n font-family: iconfont;\r\n color: red;\r\n }\r\n\r\n span {\r\n position: relative;\r\n }\r\n \u003C/style>\r\n \u003C/head>\r\n \u003Cbody>\r\n \u003Cp class=\"icon\">扫码付款\u003C/p>\r\n \u003Cspan class=\"icon\">我是span\u003C/span>\r\n \u003Cdiv class=\"icon\">divvvvvvvvvvv\u003C/div>\r\n \u003C/body>\r\n\u003C/html>\r\n```\r\nIf this is a markdown verification error, can we make Vitepress more compatible with this type of error, or can we have a switch to enable this function\n\n### Reproduction\n\nnothing\n\n### Expected behavior\n\nsucceeful build\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz\r\n Memory: 2.88 GB / 15.85 GB\r\n Binaries:\r\n Node: 18.20.3 - C:\\Program Files\\nodejs\\node.EXE \r\n Yarn: 1.22.22 - ~\\AppData\\Roaming\\npm\\yarn.CMD \r\n npm: 10.7.0 - C:\\Program Files\\nodejs\\npm.CMD \r\n pnpm: 8.15.7 - C:\\Program Files\\nodejs\\pnpm.CMD \r\n bun: 1.1.21 - ~\\.bun\\bin\\bun.EXE\r\n Browsers:\r\n Chrome: 128.0.6613.120\r\n Edge: Chromium (127.0.2651.74)\r\n Internet Explorer: 11.0.19041.4355\r\n npmPackages:\r\n vitepress: ^1.3.1 => 1.3.1\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2887],{"name":2866,"color":2867},4188,"Element is missing end tag.","2024-09-16T04:43:59Z","https://github.com/vuejs/vitepress/issues/4188",0.74768716,{"description":2894,"labels":2895,"number":2897,"owner":2869,"repository":2870,"state":2871,"title":2898,"updated_at":2899,"url":2900,"score":2901},"### Describe the bug\n\nI noticed that certain Markdown extensions for code blocks do not work as expected in VitePress when using the **templ** language, while they work properly for other languages like **js**. Specifically:\n\n- **Not Working Properly**:\n - Focus in Code Blocks\n - Colored Diffs in Code Blocks\n - Errors and Warnings in Code Blocks\n- **Working as Expected**:\n - Line Highlighting in Code Blocks\n\nThanks\n\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-4gtyqrtf?file=docs%2Findex.md\n\nVisit the demo page by clicking the _MD Extensions Issue with Templ_ button on the homepage.\n\n\n### Expected behavior\n\nAll supported Markdown extensions for code blocks should render correctly, regardless of the specified language, as long as the language is supported by shiki. Since `templ` is a supported language, these extensions should work as expected, similar to how Line Highlighting currently works.\n\n### System Info\n\n```Text\nSystem:\n OS: macOS 15.2\n CPU: (8) arm64 Apple M3\n Memory: 434.31 MB / 24.00 GB\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 20.18.1 - ~/.nvm/versions/node/v20.18.1/bin/node\n npm: 10.8.2 - ~/.nvm/versions/node/v20.18.1/bin/npm\n pnpm: 9.15.4 - ~/Library/pnpm/pnpm\n Browsers:\n Chrome: 131.0.6778.267\n Safari: 18.2\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\n- [x] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [x] Read the [docs](https://vitepress.dev).\n- [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2896],{"name":2866,"color":2867},4515,"Markdown Extensions for Code Blocks Not Working Properly with ‘templ’ Language","2025-02-01T04:42:48Z","https://github.com/vuejs/vitepress/issues/4515",0.7478925,{"description":2903,"labels":2904,"number":2908,"owner":2869,"repository":2870,"state":2871,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### Describe the bug\r\n\r\nCurrently the page outline uses a querySelectorAll which grabs the title using `el.innerText`. \r\n\r\nIf we use `el.textContent` instead - it will copy the text exactly the same as what's in the markdown file.\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nStyle h2 tags to be `text-transform: uppercase;` then in page outline you will see that the text is hardcoded as uppercase text:\r\n\r\n\u003Cimg width=\"296\" alt=\"image\" src=\"https://user-images.githubusercontent.com/1315304/203462026-7c3b1977-b531-4ac4-aefd-5aa3c55a4a9a.png\">\r\n\r\n\r\n### Expected behavior\r\n\r\nThe page outline should not output mutated text, it should use the same text as what is in the markdown file and leave it up to the CSS to mutate text. \r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 12.6\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 1.03 GB / 32.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node\r\n Yarn: 1.22.17 - /opt/homebrew/bin/yarn\r\n npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm\r\n Browsers:\r\n Chrome: 107.0.5304.110\r\n Firefox: 107.0\r\n Safari: 15.6.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.29 => 1.0.0-alpha.29\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2905],{"name":2906,"color":2907},"theme","0754FB",1637,"Page outline should use textContent instead of innerText to avoid mutation from CSS text-transform property","2023-08-12T00:04:15Z","https://github.com/vuejs/vitepress/issues/1637",0.7490794,{"description":2914,"labels":2915,"number":2919,"owner":2869,"repository":2870,"state":2871,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Describe the bug\r\n\r\nSome of the code markdown extensions do not work when the language is `vue`.\r\n\r\nIn particular, `[!code ++]`, `[!code --]`, `[!code warning]`, `[!code error]` and `[!code focus]` just show the comments at the end of the line.\r\n\r\nChanging the language to something else fixes this, e.g. `htmx` or `ts`.\r\n\r\nThis only seems to happen in the template tags of a `vue` code block. The highlighting works absolutely fine in the script part. Please see reproduction for code examples, I can't figure out how to escape the triple backtick code blocks here! ☹️ \r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-arupmh?file=docs%2Fexample.md\r\n\r\n### Expected behavior\r\n\r\nThe markdown extensions should work correctly and highlight the lines as per [the docs](https://vitepress.dev/guide/markdown#focus-in-code-blocks).\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 14.1.2\r\n CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 488.47 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\nBinaries:\r\n Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node\r\n Yarn: 1.22.10 - /usr/local/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm\r\nBrowsers:\r\n Chrome: 120.0.6099.234\r\n Firefox: 112.0.2\r\n Firefox Developer Edition: 107.0\r\n Safari: 17.1.2\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2916],{"name":2917,"color":2918},"upstream","BF29ED",3503,"Markdown code extensions don't work in some situations","2025-02-01T04:42:47Z","https://github.com/vuejs/vitepress/issues/3503",0.7557179,{"description":2925,"labels":2926,"number":2928,"owner":2869,"repository":2870,"state":2871,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Describe the bug\n\nhttps://stackblitz.com/edit/vite-j7cesz?file=docs/index.md is the repro. Its `index.md` compiles just fine with some other established markdown compilers -- I tried pandoc and it worked well.\r\n\r\nI would like to know what's wrong with my markdown code! It can be that I don't understand the VitePress markdown syntax well enough, or maybe I am lucky to find a bug in the compiler 😉 I would like to provide additional info amap.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-j7cesz?file=docs/index.md\n\n### Expected behavior\n\nCompiles just fine.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)\r\n CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H\r\n Memory: 5.91 GB / 7.61 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 19.2.0 - /usr/bin/node\r\n npm: 8.19.3 - /usr/bin/npm\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.30 => 1.0.0-alpha.30\r\n```\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2927],{"name":2866,"color":2867},1673,"VitePress does not compile a HTML-markdown mixed file saying that 'Element is missing end tag'","2023-01-21T14:17:06Z","https://github.com/vuejs/vitepress/issues/1673",0.75663126,{"description":2934,"labels":2935,"number":2937,"owner":2869,"repository":2870,"state":2871,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Describe the bug\n\nts Symbol error:\r\n\r\nPartial\u003CT>\n\n### Reproduction\n\nPartial\u003CT>\n\n### Expected behavior\n\nPartial\u003CT> is OK\n\n### System Info\n\n```sh\nSystem:\r\n OS: macOS 14.0\r\n CPU: (10) arm64 Apple M1 Max\r\n Memory: 334.34 MB / 32.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 19.5.0 - ~/.nvm/versions/node/v19.5.0/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.4.1 - ~/.nvm/versions/node/v19.5.0/bin/npm\r\n pnpm: 8.6.12 - ~/.nvm/versions/node/v19.5.0/bin/pnpm\r\n Browsers:\r\n Chrome: 115.0.5790.170\r\n Safari: 17.0\r\n npmPackages:\r\n vitepress: 1.0.0-beta.7 => 1.0.0-beta.7\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2936],{"name":2866,"color":2867},2764,"Element is missing end tag","2023-08-17T00:04:09Z","https://github.com/vuejs/vitepress/issues/2764",0.75940263,{"description":2943,"labels":2944,"number":2949,"owner":2869,"repository":2870,"state":2871,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Describe the bug\n\nRunning firefox's accessibility tests fails on \"toggle dark mode\" switch.\r\nhttps://developer.mozilla.org/en-US/docs/Web/Accessibility/Understanding_WCAG/Text_labels_and_names#form_elements_should_have_a_visible_text_label\r\n\r\na11y accessibility wcag\n\n### Reproduction\n\n- build a basic website\r\n- inspect it with the browser's console accessibility tool\n\n### Expected behavior\n\nall form input elements must have a label or attribute `aria-labelled=` with accessible value\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.10 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)\r\n CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz\r\n Memory: 11.91 GB / 12.31 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v16.15.1/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v16.15.1/bin/npm\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.49 => 1.0.0-alpha.49\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2945,2946],{"name":2906,"color":2907},{"name":2947,"color":2948},"a11y","fbca04",2080,"form elements must have a visible label","2023-03-22T00:03:24Z","https://github.com/vuejs/vitepress/issues/2080",0.7604798,{"description":2955,"labels":2956,"number":2959,"owner":2869,"repository":2870,"state":2871,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Describe the bug\r\n\r\nIn the light theme, a span of formatted code has the same background color as the striped rows of the table.\r\n\r\n| Element | Var | Value in light theme |\r\n| --- | --- | --- |\r\n| .vp-doc tr:nth-child(2n) | `--vp-c-bg-soft` | #f6f6f7 |\r\n| :not(pre) > code | `--vp-c-mute` | #f6f6f7 |\r\n\r\n### Reproduction\r\n\r\nRender this table with the default theme in light in VitePress:\r\n\r\n```md\r\n| Element | Var | Value in light theme |\r\n| --- | --- | --- |\r\n| .vp-doc tr:nth-child(2n) | `--vp-c-bg-soft` | #f6f6f7 |\r\n| :not(pre) > code | `--vp-c-mute` | #f6f6f7 |\r\n```\r\n\r\n### Expected behavior\r\n\r\nThere is a contrast between the background of the code span and all table rows, like here on GitHub.\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (16) x64 Intel(R) Xeon(R) W-11955M CPU @ 2.60GHz\r\n Memory: 13.44 GB / 31.73 GB\r\n Binaries:\r\n Node: 18.12.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 9.8.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (114.0.1823.79)\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.5 => 1.0.0-beta.5\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nSuggestion: tone down the mute colors in the light theme a bit. This makes code spans also more visible on the default white background.\r\n\r\n```scss\r\n:root {\r\n --vp-c-mute: #eeeef0; // luv = 94\r\n --vp-c-mute-light: #f3f3f9; // luv = 96\r\n --vp-c-mute-lighter: #f9f9fa; // luv = 98\r\n}\r\n```\r\n\r\n[HSLuv system](https://www.hsluv.org/) used.\r\n\r\n### Validations\r\n\r\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2957,2958],{"name":2906,"color":2907},{"name":2947,"color":2948},2610,"No contrast of code on table row in light theme","2023-08-16T00:04:20Z","https://github.com/vuejs/vitepress/issues/2610",0.7631821,["Reactive",2965],{},["Set"],["ShallowReactive",2968],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzSv6wLL-q88SA_pZ2oGnARecoIe7lNOtILFtPiVs7AE":-1},"/vuejs/vitepress/759"]