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
From this point forward, the custom EventTarget will be tied to the JavaScript className to bridge JavaScript and Dart.
However, some front-end bundling tools might alter the JavaScript className, shortening it for optimization purposes.
If plugin developers use these bundling tools and inadvertently modify the ClassName in their codes, unexpected bugs could occur.
We need a more explicit approach for our EventTarget registration. For example:
class YourEventTargetName extends EventTarget {} mercury.defineEventTarget('YourEventTargetName', YourEventTargetName);
The text was updated successfully, but these errors were encountered:
No branches or pull requests
From this point forward, the custom EventTarget will be tied to the JavaScript className to bridge JavaScript and Dart.
However, some front-end bundling tools might alter the JavaScript className, shortening it for optimization purposes.
If plugin developers use these bundling tools and inadvertently modify the ClassName in their codes, unexpected bugs could occur.
We need a more explicit approach for our EventTarget registration. For example:
The text was updated successfully, but these errors were encountered: