-
Notifications
You must be signed in to change notification settings - Fork 104
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
update to version 3.4 throw ex :[Right-hand side of 'instanceof' is not an object] #184
Comments
This issue was fixed when I retreated to version 3.3. |
Can you give me a repro on JSFiddle? I can't really debug from here. |
Same error here, unfortunately I also cannot give you a repro. The call is something like domtoimage.toPng(someElement, { bgColor: '#fff', height, width }).then(dataUrl => ...) It seems the problem is in |
Pushing v3.4.2 to see if that fixes it... reverting part of a PR I merged. |
Please verify or deny if v3.4.2 fixes this @pschmiedelenbw and @liva0126 |
That seems to fix the problem, thanks! |
Hi @IDisposable , it seems breaks the slotted element, can you please double check release 3.4.2 with #178 |
Fixed in v3.4.3 |
v3.4.3 is broken here with this error, 3.4.2 works. No ShadowDom in use, just a regular element. |
I have no issues to use 3.4.3 with regular elements (no shadow dom), see the example: https://jsfiddle.net/CWenyu/rh4Ljqa5/5/ |
I use 3.4.3, il still has this probem, so I retreated to version 3.3 |
@IDisposable
I am not sure the reason behind this but it is producing different output. Edit: I am not blocked by this issue, since 3.4.2 consists of |
3.4.2 consist of revert of this issue, so its safe to use 3.4.2 in case you want |
How about v3.4.4 just released @codesculpture @cannot-hero @ktdd |
@IDisposable i just tried v3.4.4, still have this problem |
I can't reproduce this anywhere, can you contribute a test to the .spec.js file? |
Can we reopen this (this issue is not listed on my home page, where it seems only opened issues would pop up there, i need to manually come to the repo find this issue to comment) |
Duplicated this issue (since this is closed) here |
This been addressed here #189 |
No description provided.
The text was updated successfully, but these errors were encountered: