You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
toDataURL is an export method, not a user-initiated re-render operation. Triggering render hooks might mislead developers into thinking the canvas is being redrawn on the screen, while it is actually just generating image data.
If toDataURL triggers hooks, time-consuming operations within the hooks could cause unnecessary performance degradation.
To maintain consistency, we could add an option that allows developers to choose not to skip hooks (default to skipping for better performance): canvas.toDataURL({ skipHooks: false });
no we are not adding more options, that is for sure.
ToDataUrl should mimic more or less what toCanvasElement does, and all of them need to render the canvas again.
On the other side if you are using after:render to modify the render, you may want it into your export as well.
The safest thing to do could be to try to emit during the event the type of render that is happening, normal, toDataUrl, toCanvasElement or whatever. But i think that could be slightly complicated.
CheckList
Version
6.0.2
In What environments are you experiencing the problem?
No response
Node Version (if applicable)
None
Link To Reproduction
https://codepen.io/zhe-he-the-vuer/pen/EaYLxLB
Steps To Reproduce
Expected Behavior
Actual Behavior
Error Message & Stack Trace
No response
The text was updated successfully, but these errors were encountered: