275100 2024-06-04 01:48:49 -0700 CanvasBase owns a ImageBuffer that belongs to the CanvasRenderingContext 2026-02-27 03:13:08 -0800 1 1 1 Unclassified WebKit Canvas WebKit Local Build Unspecified Unspecified RESOLVED FIXED InRadar P2 Normal --- 274750 275105 275144 275201 275563 275902 277478 306603 306606 306608 306613 306617 308815 267291 273622 1 kkinnunen kkinnunen sabouhallawa simon.fraser webkit-bug-importer oldest_to_newest 2039609 0 kkinnunen 2024-06-04 01:48:49 -0700 CanvasBase owns a ImageBuffer that belongs to the CanvasRenderingContext This is a problem because only CanvasRenderingContext2DBase really uses the ImageBuffer. Others would be better performing if the CanvasBase didn't have a ImageBuffer, rather the buffer was asked from the context. 2039611 1 webkit-bug-importer 2024-06-04 01:49:19 -0700 <rdar://problem/129208981> 2044906 2 simon.fraser 2024-07-05 21:04:07 -0700 > the buffer was asked from the context This seems backwards. The buffer vends the context. 2049793 3 kkinnunen 2024-07-31 04:32:37 -0700 (In reply to Simon Fraser (smfr) from comment #2) > > the buffer was asked from the context > This seems backwards. The buffer vends the context. The intention was to say "the |drawing or display] buffer copy was asked from the [canvas rendering] context". In this context "buffer vends the context" doesn't make sense. The specific variant of canvas rendering context should return the rendering results image, it is private logic of said rendering type. The specific variant of canvas rendering context should manage the drawing buffer backing store in the manner it needs to manage it. 2179401 4 kkinnunen 2026-02-09 04:07:22 -0800 Pull request: https://github.com/WebKit/WebKit/pull/58197 2181185 5 ews-feeder 2026-02-13 01:37:58 -0800 Committed 307450@main (39eb51251d8f): <https://commits.webkit.org/307450@main> Reviewed commits have been landed. Closing PR #58197 and removing active labels.