We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bunch of font api calls, it makes performance issue. when i call domToImage
const cssToImage = async (parentDiv) => { const scale = 4; const options = { width: parentDiv.clientWidth * scale, height: parentDiv.clientHeight * scale, style: { left: 0, top: 0, right: 0, bottom: 0, transform: "scale(" + scale + ")", transformOrigin: "center center", }, }; parentDiv.querySelector("svg").style.animationName = "none"; console.log(parentDiv.querySelector("svg").style) const dataUrl = await domToImage.toPng(parentDiv, options); return { dataUrl }; };
"dom-to-image-more": "^2.10.1"
Chromium Version 112.0.5615.49
The text was updated successfully, but these errors were encountered:
Can we get some more details on the URLs in the "Name" column, or better yet a jsfiddle? Also, have you tried the cacheBusting option on/off?
Sorry, something went wrong.
No branches or pull requests
Use case: description, code
Bunch of font api calls, it makes performance issue. when i call domToImage
const cssToImage = async (parentDiv) => { const scale = 4; const options = { width: parentDiv.clientWidth * scale, height: parentDiv.clientHeight * scale, style: { left: 0, top: 0, right: 0, bottom: 0, transform: "scale(" + scale + ")", transformOrigin: "center center", }, }; parentDiv.querySelector("svg").style.animationName = "none"; console.log(parentDiv.querySelector("svg").style) const dataUrl = await domToImage.toPng(parentDiv, options); return { dataUrl }; };
Actual behavior (stack traces, console logs etc)
Library version
"dom-to-image-more": "^2.10.1"
Browsers
Chromium Version 112.0.5615.49
The text was updated successfully, but these errors were encountered: