Error "operation is insecure" raised when trying to preview a markdown file in VS Code

[l0rd]

Describe the bug

The following error is shown when trying to open a Markdown file

Che version

next (development version)

Steps to reproduce

I am using the dogfooding instance. Open a project that includes a markdown file using a factory link. Open the markdown file and click on the preview icon:

Expected behavior

See the html rendered markdown version of the file I am editing.

Runtime

OpenShift

Installation method

OperatorHub

Environment

other (please specify in additional context)

[l0rd]

cc @azatsarynnyy

[l0rd]

Setting > Markdown > Change Preview Settings Security > Disable doesn't seem to help:

[azatsarynnyy]

@l0rd could you attach some test project to reproduce the issue? Maybe there's some specific content that can't be rendered. As it is not reproduced for any markdown file.

[l0rd]

I was able to reproduce it on 3 different repos I have opened today:

• cri-o
• devspaces-demo
• docker-hello

[l0rd]

I am using Firefox.

[azatsarynnyy]

I checked it with the docker-hello project in Firefox

and didn't notice any issues

It might be reproduced on Mac only. @RomanNikitenko could you check it on your side, please?

[RomanNikitenko]

I can not reproduce the problem for Chrome. But I'm able to reproduce it for Firefox on Mac system.

[l0rd]

I am reducing the severity considered that it's only reproducible on Firefox on a mac (or maybe it's the version? Mine is different from Artem's and it is version 102.04.0esr).

[RomanNikitenko]

About version - I use the following:

[azatsarynnyy]

Thank you @RomanNikitenko for verifying the issue on Mac.

[RomanNikitenko]

Today I checked it for the Codespaces- the issue is not actual for the Codespaces. But now I can not reproduce the problem for the Che-Code on the dogfooding instance as well.

So, maybe it was fixed recently in the upstream. It would be nice if someone could double-check it to confirm.

[azatsarynnyy]

So, maybe it was fixed recently in the upstream.

I see there were several WebView-related patches upstream last week.

@l0rd could you please recheck it to confirm if the issue is still relevant for you?

[azatsarynnyy]

https://github.com/eclipse/che/issues/21852#issuecomment-1333509295

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.