We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
Uncaught runtime errors: ERROR DataCloneError: Proxy object could not be cloned.
To Reproduce Steps to reproduce the behavior:
Expected behavior
Close tab successfully and no error was thrown.
Screenshots
Desktop (please complete the following information):
Additional context
I'm using the source code, and run pnpm start in debugging mode.
pnpm start
In the debug inspect console, I can see the error and its stack trace as below.
Expand the stack trace can see the following image:
Click on it can see the source code:
I believe it has something to do with firefox itself since the error source is in firefox. But I'm wondering if we could do anything to avoid this.
The text was updated successfully, but these errors were encountered:
Hi @noscripter,
Thanks for reporting this. I have two questions:
Sorry, something went wrong.
I can reproduce now, the problem happens only in dev model (start command) but not build. I guess it might be related to dev utility like StrictMode.
start
build
StrictMode
No branches or pull requests
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Close tab successfully and no error was thrown.
Screenshots
Desktop (please complete the following information):
Additional context
I'm using the source code, and run
pnpm start
in debugging mode.In the debug inspect console, I can see the error and its stack trace as below.
Expand the stack trace can see the following image:
Click on it can see the source code:
I believe it has something to do with firefox itself since the error source is in firefox. But I'm wondering if we could do anything to avoid this.
The text was updated successfully, but these errors were encountered: