Skip to content
New issue

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

Handle disabled behavior #22

Open
andrejewski opened this issue Jun 30, 2017 · 2 comments
Open

Handle disabled behavior #22

andrejewski opened this issue Jun 30, 2017 · 2 comments

Comments

@andrejewski
Copy link
Contributor

andrejewski commented Jun 30, 2017

We should check out the disabled behavior @christopherjbaker ran into in canjs/can-util#294.

I don't know if it merits a code change here, I just want to understand the behavior and potentially normalize. I do not want to include the warning.

@chasenlehara
Copy link
Member

@andrejewski What should be the next steps for this issue?

@andrejewski
Copy link
Contributor Author

Not a priority, but this warning can be ported over to can-dom-events dispatch method.

I say non priority as this warning was only made necessary by our flaky can-util mutation tests. This detection may be a hack for an unrelated problem which is not evident to this project's tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants