Yulong Wang

> If we pass the MLContext thru a session options, my understand is that we'll need to a way store the the MLContexts in JS, pass an id to to...

> Thanks @fs-eire, @huningxin, good idea, thus @egalli could continue his [PR](https://github.com/microsoft/onnxruntime/pull/20600). > > Now only one remaining issue, my concern is passing specific webnn options to backend initialization does...

> Even if we pass the MLContext, we would still need to pass the deviceType to the C++ code as it is used to select between NCHW and NHWC. >...

> > > Thanks @fs-eire, @huningxin, good idea, thus @egalli could continue his [PR](https://github.com/microsoft/onnxruntime/pull/20600). > > > Now only one remaining issue, my concern is passing specific webnn options to...

> > Yes, but the implementation can be different. Actually we can do this in JS: > > if there is not MLContext in session options, try to create a...

I think before WebNN allows getting the options from a `MLContext` object, it seems that we need users to pass both `deviceType` and `powerPreference` in session options. If MLContext is...

I don't think this is a clean solution. A better solution would be exposing properties for getting those metadata from the MLContext object, which may require a spec review process....

The current implementation has a few problems: - If user specify multiple execution providers (which is legit in ORT) like `['webgpu', { name: 'webnn', powerPreference: 'high-performance' }]`, it is hard...

Add a few comments here: There is a new issue (#20729) reveals a clearer picture of how an actual requirement would be. Users may want to manipulate with the `MLContext`...

I think the usage of Promise has no problem. I need more information (error messages or stacktrace or whatever) to know why it does not work on windows app. just...