review SubtleCrypto fallback scenarios

[lewing]

Once #65966 lands we will still fall back to the managed implementation if the page is not served with CORS headers. Should there be a user indication of this state, and if so, through what mechanism.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Once #65966 lands we will still fall back to the managed implementation if the page is not served with CORS headers. Should there be a user indication of this state, and if so, through what mechanism.

Author:	lewing
Assignees:	-
Labels:	arch-wasm
Milestone:	7.0.0

[ghost]

Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Once #65966 lands we will still fall back to the managed implementation if the page is not served with CORS headers. Should there be a user indication of this state, and if so, through what mechanism.

Author:	lewing
Assignees:	-
Labels:	arch-wasm, area-System.Security
Milestone:	7.0.0

[radical]

@SteveSandersonMS does anything need to be done for 7.0 here? If so, then what should be done?

[radical]

Moving to 8.0 . @SteveSandersonMS @javiercn Feel free to move this to 7.0, if you feel something needs to be done here.

[SteveSandersonMS]

@radical @lewing In light of #73858, should this issue just be closed, or do we need to move any of it into that tracking issue?

[radical]

Yes, we can close this. thanks:)