-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
IE 11 "path" not found error with the v0.5.0-beta4 #1213
Comments
Please share an example on jsfiddle |
Hi sorry for the late reply. I've been spending days to recreate it on the fiddle. In the process I figured out what was wrong with mine. So feel free to look at what I did and close the ticket or add more explanation as you will. Here are what I found: 1.) IE11 does not pass the is browser native svg logic in the library, this.support.svg is false. https://jsfiddle.net/kevin074/fd0zszhb/15/ Now my downloaded image is not accurate to my app. I have yet to begin to debug the problem, but if you see anything that seems fishy from what I wrote, PLEASE let me know. |
Forgot to comment. I've found the solution. I used canvg to change SVG -> canvas, and then use html2canvas to generate the rest of the picture. Here is the code i used to integrate the svg
You'd need to re-show the original svg and remove the canvas element after you are done with it. |
Hi we've implemented html2canvas and image can be downloaded on chrome fine (with some tweeks still needed), but the same code on IE11/Edge shows the error:
"path" argument is required
could you explain more in detail what does this error mean exactly and if there are typical mistakes that would cause this error.
we are also using bluebird as our promise library. Added in window.Promise = bluebird in our code.
here is how we are currently calling html2canvas
var elem = $([SELECTOR])[0];
var height, width = from elem.height (width)
html2canvas(elem, {
height: height,
width: width,
scale: 2,
logging: true,
onclone: [CUSTOM FUNCTION HERE]
}).then(function (canvas) { ... })
The text was updated successfully, but these errors were encountered: