Opening shared playground workflow link in new tab results in empty playground (Crtl + Click or Click on Wheel)

[TobiasNx]

When clicking on a workflow link with Ctrl+Click or mouse wheel to open it in another tab an empty playground is opened. instead of the shared workflow.

Test 1: Plain link without markdown does not work:
https://metafacture.org/playground/?flux=inputFile%0A%7Copen-file%0A%7Cas-lines%0A%7Cdecode-json%0A%7Cfix%28transformationFile%29%0A%7Cencode-xml%28rootTag%3D%22collection%22%29%0A%7Cprint%0A%3B&transformation=move_field%28%22_id%22%2C+%22id%22%29%0Amove_field%28%22a%22%2C+%22title%22%29%0Apaste%28%22creator%22%2C+%22b.v%22%2C+%22b.n%22%2C+%22~aus%22%2C+%22c%22%29%0Aretain%28%22id%22%2C+%22title%22%2C+%22creator%22%29&data=%7B%22a%22%3A+%22Faust%22%2C+%22b%22%3A+%7B%22n%22%3A+%22Goethe%22%2C+%22v%22%3A+%22JW%22%7D%2C+%22c%22%3A+%22Weimar%22%7D%0A%7B%22a%22%3A+%22R%C3%A4uber%22%2C+%22b%22%3A+%7B%22n%22%3A+%22Schiller%22%2C+%22v%22%3A+%22F%22%7D%2C+%22c%22%3A+%22Weimar%22%7D

Test 2: "Normal" Markdown link does not work: Test 2

Test 3: HTML Link does not work: Test3

Test 4 HTML Link with target=blank works to open the link in new tab WITH content when clicking witout CTRL. When using CTRL then it does not work: Test 4 Github does not support target blank

Note example links do work: https://metafacture.org/playground/?example=Local+JSON+to+XML+%28fix%29

[TobiasNx]

If one is quick, you can see, that the correct URL is in the URL bar at first but while loading then switches to https://metafacture.org/playground/ and provides an empty playground.

[dr0i]

Can you test it again @TobiasNx ? On my environement it works, probably after #201.

[TobiasNx]

Now this seems to be a arbitrary sometimes it has content and sometimes it does not.

Sometimes like this:

Sometimes like this:

[dr0i]

So, have we some progress here? Before #201 it never worked and now at least sometimes it does? If so, it seems plausible for me to work further on moving all used resources to internal resources.

[TobiasNx]

I am not sure.

[katauber]

The problem in this case is the use of "defaultValue" instaead of "value" in the monaco-editor/react component. "defaultValue" should be used in uncontrolled components and "value" in controlled components, so "value" would be the right decision for our editors, but we had problems with the cursor position in the past. Using "defaultValue" was a quick hack to avoid problems with the cursor position.
The right solution should be to use "value" instead of "defaultValue" and handle the cursor position ourself.