-
Notifications
You must be signed in to change notification settings - Fork 31
Reactify not working in latest Chrome version #58
Comments
I only see this happening in Chrome version 55.* |
@kentendo do you have a reproduction of this? If you can write a failing test for this, that would be awesome :). Currently tests pass in 55. |
I started on a test, but looked at the other tests in here and noticed they are still using the v0 API. The issue I'm seeing is more v1 specific, where the lifecycle hooks ( onConnectedCallback, etc ) are never getting called. Any ideas? |
You're right. We should update the tests, for sure. I raised #59 for this. I don't have much time to do this for the next week or so. Would you have time to submit a PR for it? I understand if not. |
I'll give it a shot... |
I've made some good progress on #59, but I'm having issues with the event tests in chrome... |
@treshugart
Reactified component is rendering in Firefox, but not in latest Chrome (55.0.2883.95).
Component gets inserted inserted into DOM but is never upgraded and never renders itself.
See codepen below...
http://codepen.io/kentendo/pen/BQMEbe?editors=1010
The text was updated successfully, but these errors were encountered: