|Issue 2122||Canvas maximum size >32767px|
|Starred by 8 users||Reported by voidvol...@gmail.com, Feb 3 2014||Back to list|
Feb 4 2014,
Assign to Mike to take a look and see if you think there is something we can do about this issue.. Stephen noted in the Chromium bug that it is a known limitation of Skia's design that we may not fix, but voidvolker opened here for our consideration.
Oct 14 2014,
Dec 7 2015,
Mar 2 2016,
Given that Chrome draws to tiles, wouldn't it be reasonable to attack this at that level rather than in Skia? Florin, do you think there is any interest in limiting the SkCanvas to something < 32K in Chrome, and then tiling additional SkCanvas to make the width specified the as described above?
Mar 2 2016,
I think canvas2d is not (always?) tiled - junov, would it make sense to limit the size in Blink?
Mar 7 2016,
Correct, canvases are never tiled in the current implementation. No need to have a limit that is explicitly known to blink since blink knows when the canvas is to big by the fact of skia failing to allocate it. That being said, Houdini's custom paint feature is going to offer a very reasonable workaround for drawing arbitrarily large things using a write-only subset of the Canvas API. That will leverage tiling.
Jul 13 2016,
This issue is causing chrome://tracing to not display large traces (https://github.com/catapult-project/catapult/issues/2416#issuecomment-232327904). Are there any plans to address it in the near future?
|► Sign in to add a comment|