Closed Bug 1646545 Opened 4 years ago Closed 4 years ago

Figure out if GetInProcessScriptableTop usage in WebSocket.cpp is OK.

Categories

(Core :: DOM: Networking, task, P1)

task

Tracking

()

RESOLVED FIXED
82 Branch
Fission Milestone M6b
Tracking Status
firefox82 --- fixed

People

(Reporter: kmag, Assigned: valentin)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

It's used in a bunch of places, mostly (though not always) just to get the top inner window ID. That can be done (and more correctly) using WindowContext instead. I'm not sure what needs to happen with the other uses.

Severity: -- → N/A
Priority: -- → P3
Whiteboard: [necko-triaged]

Tracking "Figure out GetInProcessTop usage" bugs for Fission M6b.

Fission Milestone: --- → M6b

Nhi, please assign someone to look into this.

Flags: needinfo?(nhnguyen)
Flags: needinfo?(nhnguyen) → needinfo?(juhsu)

I'll take a look

Assignee: nobody → juhsu
Flags: needinfo?(juhsu)
Priority: P3 → P1
Flags: needinfo?(valentin.gosu)
Assignee: juhsu → valentin.gosu
Flags: needinfo?(valentin.gosu)
Blocks: 1660968
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/75c91a941601
Replace GetInProcessScriptableTop usage with TopWindowContext() in WebSocket.cpp r=baku
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: