* feat: add WebFrameMain detached property fix: throw instead of returning null senderFrame test: detached frames fix: ensure IPCs of pending deletion RFHs are dispatched fix: lookup WFM by FTN ID to dispatch IPCs feat: add frame.isDestroyed() return null fix: return undefined docs: add null to all frame properties refactor: option c, return null and emit warning refactor: add routingId & processId to navigation events test: null frame property docs: clarify warning message better wording clarify null frame fix: browserwindow spec * maybe fix 🤷 * fix: use updated util #43722 * docs: add notice for frame change of behavior * docs: clarify why frame properties may be null * lint * wip * fix: content::FrameTreeNodeId lookup and converter * refactor: avoid holey array deoptimization --------- Co-authored-by: John Kleinschmidt <jkleinsc@electronjs.org>
1,010 B
1,010 B
IpcMainEvent Object extends Event
processIdInteger - The internal ID of the renderer process that sent this messageframeIdInteger - The ID of the renderer frame that sent this messagereturnValueany - Set this to the value to be returned in a synchronous messagesenderWebContents - Returns thewebContentsthat sent the messagesenderFrameWebFrameMain | null Readonly - The frame that sent this message. May benullif accessed after the frame has either navigated or been destroyed.portsMessagePortMain[] - A list of MessagePorts that were transferred with this messagereplyFunction - A function that will send an IPC message to the renderer frame that sent the original message that you are currently handling. You should use this method to "reply" to the sent message in order to guarantee the reply will go to the correct process and frame.channelstring...argsany[]