don't retain port in content scripts #285
Conversation
| import { createPenumbraStateEvent } from '@penumbra-zone/client/event'; | ||
| import type { PenumbraProvider } from '@penumbra-zone/client/provider'; |
There was a problem hiding this comment.
not strictly necessary, but due to poor webpack tree-shaking, importing from the root package apparently caused the generated script to be very large.
a more specific import significantly reduces the size of the content script.
| disconnect: () => this.postDisconnectRequest(), | ||
| isConnected: () => Boolean(this.port && this.presentState === PenumbraState.Connected), | ||
| isConnected: () => this.presentState === PenumbraState.Connected, |
There was a problem hiding this comment.
i would like to do some more investigation to identify possibly unknown problems with these changes to state transitions
| private postDisconnectRequest() { | ||
| const attempt = this.listenEndMessage(); | ||
| window.postMessage(disconnectMessage, '/', []); | ||
| return attempt; | ||
| } |
There was a problem hiding this comment.
pulled this out into its own method to match the structure of the connect request logic
| if (this.presentState !== PenumbraState.Connected) { | ||
| this.setPending(); | ||
| } |
There was a problem hiding this comment.
this change needs some closer inspection too
| window.addEventListener('message', praxDocumentListener); | ||
| chrome.runtime.onMessage.addListener(praxExtensionListener); |
There was a problem hiding this comment.
can we add code comments to the two event listeners, praxDocumentListener and praxExtensionListener?
Content scripts no longer retain a
MessagePortin violation of object transfer rules.Related to penumbra-zone/web#2018