-
Notifications
You must be signed in to change notification settings - Fork 18
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
Wrapper existence check doesn't work correctly #17
Comments
- as mentioned in #17, wrapper existence check does not work for wrapperId pointing to Receiver's parent wrapper. Moving the logic back to componentDidMount solves this issue.
@horaklukas Thanks so reporting the issue and this is a very good catch! I created a PR #18 to fix this issue. FYI, the test case you mentioned above will always fail, not because of the placement of existence check, but the nature of Thanks once again for you time on checking the changes! |
Looks good, thanks for quick fix. Also big thanks for sharing the trick about mounting to the document, I did't know that before! 👍 |
I will test it tomorrow and then close the issue 😉 |
all good :) I tested a bit with the basic example and it should work. 0.4.1 is published as well. thanks once again for checking. |
Using
wrapperId
to distinguish wrapper elements of more receivers doesn't work because of check for wrapper element existence in constructor.Consider test below, it should pass, but it fails with "wrapper element with Id customId not found" error. Same happens when using it in real browser.
It's probably caused by timing check, in component constructor is too early because whole elements tree haven't fully rendered yet.
The text was updated successfully, but these errors were encountered: