doc: document diverging MessagePort.onmessage handling · nodejs/node@fdad4d2 · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 632
• Pull requests 755
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit fdad4d2

Browse filesBrowse the repository at this point in the historyBrowse files

addaleax

authored and

BridgeAR

committed

doc: document diverging MessagePort.onmessage handling

Fixes: #26463 PR-URL: #26487 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>

1 parent 73370b4 commit fdad4d2
Copy full SHA for fdad4d2

1 file changed

+3Lines changed: 3 additions & 0 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • worker_threads.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎doc/api/worker_threads.md‎

Copy file name to clipboardExpand all lines: doc/api/worker_threads.md

+3Lines changed: 3 additions & 0 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -319,6 +319,9 @@ listeners are attached.
319	319
320	320	This method exists for parity with the Web `MessagePort` API. In Node.js,
321	321	it is only useful for ignoring messages when no event listener is present.
	322	+ Node.js also diverges in its handling of `.onmessage`. Setting it will
	323	+ automatically call `.start()`, but unsetting it will let messages queue up
	324	+ until a new handler is set or the port is discarded.
322	325
323	326	### port.unref()
324	327	<!-- YAML

0 commit comments

Comments

0 (0)