Markdown field adding strange content and overflowing

[jameswoodley]

Describe the bug

Using OrchardCore.Application.Cms.Core.Targets v1.3.0 we are seeing strange behaviour with the Markdown field. Upon loading the Part it shows a collection of x:

This also happens if creating a new instance of the Content Type, the Markdown field is prefilled with the xxxxxxx until clicking on it

Clicking on the field does then show the content, however it seems to overflow it's container

This doesn't seem to be the case on the Try Orchard site https://try.orchardcore.net/qj4dh3wy/

To Reproduce

Steps to reproduce the behavior:

1. Open Content Type with markdown field
2. Click on 'the field
3. See content, however overflowing it's container

Expected behavior

As it currently works on the Try Orchard site - makes me wonder if this is an upgrade issue as we recently upgraded to v1.3.0

This could be related to #10495 ?

[dsghi]

I have a couple of issues with the Markdown field as well... hopefully, it's OK to pile on this issue...

Clicking the Toggle Preview toolbar button takes it full screen, but it ends up behind the top and left navigation. (If you first click side by side or full screen, you can switch to preview without issue):

If using the admin dark mode, the content of the markdown field is not visible:

[dsghi]

Well, it turns out this is a super easy fix to all of the above, lol - it's an issue with loading the codemirror.css - a quick workaround is to disable Use framework CDN from Settings > General > Resources tab.

Found this in the browser console: Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdnjs.cloudflare.com/ajax/libs/codemirror/5.65.2/codemirror.css' with computed SHA-384 integrity 'bsaAhvdduZPAwUb7RRLRvDgtEtOsggrgjkr/EjPO1i/vdoi+DmdLaG79UOt6M5hD'. The resource has been blocked.

Seems the SHA has changed on the CDN, when I looked they're publishing a 512 now by default, IDK if the 384 is available too, I can't seem to locate it. I've read that 384 is the most secure... but anyway.

I see this is being addressed with #11646

[dodyg]

@dsghi thank you for workaround