JSInterop support for invoking constructors, properties, and supplying callbacks

[javiercn]

• Support invoking constructor functions either detecting them automatically or with a new method.
• Support invoking callback objects (maybe this works already), either with a new JS/Dotnet callback.
• Support accessing object properties directly (automatically or via a new method).

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[javiercn]

We had several reports of these things in this area and some of them block using basic JS functionality without having to write a wrapper.

[campersau]

For wasm only apps there is https://github.com/dotnet/runtime/tree/main/src/libraries/System.Private.Runtime.InteropServices.JavaScript if you aren't afraid of the Private part.

[javiercn]

We don't recommend using those directly, since they are wasm specific and I believe might change in the future

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.