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
paper.setup(theCanvas)varhello=newpaper.PointText({point: newpaper.Point(16,16),content: 'Hello!',font: '"Latin Modern Math"',fontSize: 16,});varbackground=newpaper.Shape.Rectangle(newpaper.Point(10,10),newpaper.Size(40,889005130))background.fillColor=newpaper.Color(1,0,0,0.5);
Expected output:
Actual output (in chrome and firefox respectively):
Note how the rectangle in chrome moved (the bottom of the rectangle is visible while the top is no longer visible). And the rectangle in Firefox decided to move on to better geometry or is totally invisible.
This bug is reproducible using the JavaScript above. Remove the least significant digit from the height and it renders correctly again.
I tried to render a 30 hour video using paperjs on a rather big canvas. After a week of rendering this bug was discovered.
The text was updated successfully, but these errors were encountered:
I am fairly certain this is the same problem as #823, which has been determined to be a Canvas limitation that is really difficult to overcome in paper.js, as it depends on vendor implementations of the Canvas API and is therefore unpredictable… Could you work around it in your own code?
What we should do though is create a simplified test-case similar to #823 (comment) and log separate issues with the browser vendors for this behavior...
Observe the following program:
Expected output:
Actual output (in chrome and firefox respectively):
Note how the rectangle in chrome moved (the bottom of the rectangle is visible while the top is no longer visible). And the rectangle in Firefox decided to move on to better geometry or is totally invisible.
This bug is reproducible using the JavaScript above. Remove the least significant digit from the height and it renders correctly again.
I tried to render a 30 hour video using paperjs on a rather big canvas. After a week of rendering this bug was discovered.
The text was updated successfully, but these errors were encountered: