-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Cannot read property 'eventName' of undefined #14888
Comments
until emberjs/ember.js#14888 is fixed
Thank you for reporting!!! @GavinJoyce - This is related to the event dispatcher refactors, mind taking a look? |
you're welcome! :D small addition, the same error is thrown when that component is added back to the view. also demonstrated in that twiddle. |
Sure, I'll take a look |
It looks like this guard is needed: I'm working on a test now |
Oh no! There was even a comment explaining why it was needed. If only we had a test too... |
I'm having trouble creating a failing test. I believe that this should fail, but it doesn't: |
I could manually unregister the action and ensure that an exception isn't thrown, but I'd much rather use the high level API to drive the test. Suggestions welcome |
Looks like Firefox doesn't throw, but Chrome does. Can you run your travis build in Chrome? |
I haven't yet managed to create a failing test in Chrome |
ah. hm. these are the userland tests that fail: https://circleci.com/gh/nypublicradio/nypr-account-settings/52 |
@noslouch thanks, can you point me to the source of a failing test? |
ah, it's an acceptance test: https://github.com/nypublicradio/nypr-account-settings/blob/master/tests/acceptance/server-error-test.js |
oh, I see. I need to trigger a |
The fix is here: #14890 It's late here are creating a failing test is proving tricky. I think we should merge the fix and leave this issue open until I follow up with a test later this week |
[BUGFIX beta] fix #14888 with a guard
Here's a (non-ideal IMO) test which will prevent a regression: #14889 |
use focus in better code
add a test to prevent regression of #14888
Fixed in #15080 |
I've got a component which is conditionally rendered based on the value of a boolean. If that boolean value is changed by an action from within that component, the above error is thrown when the component is removed from the view.
Seems like it was introduced with canary and is happening from
2.13.0-alpha.1-canary+96c0bb79
onward.Here's a simple twiddle demonstrating: https://ember-twiddle.com/b86adfba657f450a4d264e01a3fb0d37?openFiles=templates.application.hbs%2Ctemplates.components.my-component.hbs
Seems related to #1643. The stack trace points to the same block patched by pivotal-topher-bullock@74e0d58.
Stack trace:
The text was updated successfully, but these errors were encountered: