It looks like the problem occurs when trying to use the secure websockets from this sandbox'ed iframe: ``` <iframe _ngcontent-upv-c544="" sandbox="allow-scripts allow-downloads" src="https://localhost:3000?v=fb166ce&reportId=dev&bookmark=default"></iframe> ``` Specifically, we do in fact fail [here](https://searchfox.org/mozilla-central/rev/3cb31675aeffd10f1f6ae7c40e24b254da7798e5/dom/websocket/WebSocket.cpp#2839), as Kershaw pointed out in Comment 10. In this case I see these fields on the windowContext: `IsTop(): 1` and `SameOriginWithTop(): 0` But I will need help from someone with a better understanding of navigating the window contexts. Maybe we have some common code for determining the principal?
Bug 1748005 Comment 31 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It looks like the problem occurs when trying to use the secure websockets from this sandbox'ed iframe: ``` <iframe _ngcontent-upv-c544="" sandbox="allow-scripts allow-downloads" src="https://localhost:3000?v=fb166ce&reportId=dev&bookmark=default"></iframe> ``` Specifically, we do in fact fail [here](https://searchfox.org/mozilla-central/rev/3cb31675aeffd10f1f6ae7c40e24b254da7798e5/dom/websocket/WebSocket.cpp#2839), as Kershaw pointed out in Comment 10. In this case I see these fields on the windowContext: `IsTop(): 1`, `SameOriginWithTop(): 0`, `IsSecureContext(): 1` But I will need help from someone with a better understanding of navigating the window contexts. Maybe we have some common code for determining the principal?