Markdown for Jekyl is being displayed wrongly as strikethrough

[claresudbery]

Type: Bug

Hi
I have markdown files for Jekyl which have a header section in each file, and VS Code is interpreting the header delineators to mean strikedown.
Headers look like this:

---
layout: page
location: pages/think/code-princ/architecture/leaf
permalink: /pages/think/code-princ/architecture/Clean-vs-Hexagonal-Architecture
---

The three hyphens are suddenly being interpreted to mean strikethrough on content later in the code. This did not used to happen, and it doesn't happen in the regular (non-Insiders) version of VS Code.
I can't attach a screenshot, so below is an attempt to describe it in simplified terms.
The following file content is problematic in Insiders, but not in ordinary VS Code:

---
title: Header info (it seems important that the three hyphens above are the very first line of the file)
title: header info (it seems to be adding a second line in here that causes the problem to appear)
---
## section header
THIS TEXT IS FINE
## another header
THIS TEXT IS SHOWN AS STRIKETHROUGH N INSIDERS, BUT NOT IN ORDINARY VS CODE

VS Code version: Code - Insiders 1.92.0-insider (34f8428, 2024-07-04T05:50:23.194Z)
OS version: Darwin x64 22.6.0
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz (8 x 2300)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	21, 13, 8
Memory (System)	16.00GB (0.02GB free)
Process Argv	--crash-reporter-id b99c6464-0333-4ef8-9265-c02ad50b5035
Screen Reader	no
VM	0%

Extensions: none

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
vstes627:30244334
vscod805:30301674
vsaa593:30376534
py29gd2263:31024238
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythonregdiag2:30926734
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
jchc7451:31067543
chatpanelt:31014475
724cj586:31013169
a69g1124:31018687
dvdeprecation:31040973
dwnewjupyter:31046869
2f103344:31071589
impr_priority:31057980
nativerepl1:31071684
refactort:31084545
pythonrstrctxt:31089940
0c838689:31088353
1iic9185:31091668

[RedCMD]

dup of #220022

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

[mjbvz]

Should be fixed in current insiders builds