Check-canvas-instance-in-another-window #507
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
Currently, when creating root and checking if target is
HTMLCanvasElement
we check it withtarget instanceof HTMLCanvasElement
It will break in quite rare-use case, when rendering content into another window (created with
const newWindow = window.open()
using React portal.In this case - created canvas is instance of
newWindow.HTMLCanvasElement
, not globalHTMLCanvasElement
(or technicallywindow.HTMLCanvasElement
). As a result - the app will crash.Use case for such a scenario is eg. creating multi-window Electron applications, when child windows are created using
window.open()
. I described this architecture in detail here: https://pietrasiak.com/creating-multi-window-electron-apps-using-react-portalsFixes:
I added
getIsCanvasElement
function that is checking for this case and modified createRoot function to use it when checking if target is canvas.Pre-Merge Checklist
npm run lint
)npm run test
)