1d158399a6
* feat: expose the sameSite value for cookies * Apply suggestions from code review Co-Authored-By: Charles Kerr <ckerr@github.com> * Apply suggestions from code review Align with cookie samesite values for the extensions API https://developer.chrome.com/extensions/cookies#type-SameSiteStatus * chore: add tests for sameSite cookies get/set * chore: update docs parser * chore: update docs for MessageChannel and MessagePort to have correct process information * chore: remove LOG warning * chore: throw error if the string->samesite conversion fails Co-authored-by: Charles Kerr <ckerr@github.com>
1.5 KiB
MessagePortMain
MessagePortMain is the main-process-side equivalent of the DOM
MessagePort object. It behaves similarly to the DOM version, with the
exception that it uses the Node.js EventEmitter event system, instead of the
DOM EventTarget system. This means you should use port.on('message', ...)
to listen for events, instead of port.onmessage = ... or
port.addEventListener('message', ...)
See the Channel Messaging API documentation for more information on using channel messaging.
MessagePortMain is an [EventEmitter][event-emitter].
Class: MessagePortMain
Process: Main
Instance Methods
port.postMessage(message, [transfer])
messageanytransferMessagePortMain[] (optional)
Sends a message from the port, and optionally, transfers ownership of objects to other browsing contexts.
port.start()
Starts the sending of messages queued on the port. Messages will be queued until this method is called.
port.close()
Disconnects the port, so it is no longer active.
Instance Events
Event: 'message'
Returns:
messageEventObjectdataanyportsMessagePortMain[]
Emitted when a MessagePortMain object receives a message.
Event: 'close'
Emitted when the remote end of a MessagePortMain object becomes disconnected.