Repository navigation
[2/2] fix: draw html5 frames on a software canvas so Firefox keeps their gradients - #280
Merged
dazzatronus merged 1 commit intoOct 30, 2026
Conversation
This was referenced Oct 30, 2026
dazzatronus
force-pushed
the
derk/html5-firefox-gradients
branch
from
October 30, 2026 12:36
67ec760 to
56dacaa
Compare
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 30, 2026
## [2.30.1](v2.30.0...v2.30.1) (2026-10-30) ### Bug Fixes * draw clip filters in the preview as the render applies them ([#265](#265)) ([ac02f9b](ac02f9b)) * draw html5 frames on a software canvas so Firefox keeps their gradients ([#280](#280)) ([d508db8](d508db8)) * **export:** draw export frames into one stencil target so Firefox keeps masked content ([#278](#278)) ([f431c6b](f431c6b)) * **export:** tag browser exports as limited range so Safari's whites stay white ([#277](#277)) ([c6150eb](c6150eb)) * keep a frame's embedded images when Safari draws an html5 clip ([#279](#279)) ([5154007](5154007)) * keep baking html5 clips while their tab is in the background ([#281](#281)) ([e1fa158](e1fa158))
|
🎉 This PR is included in version 2.30.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Oct 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Firefox's GPU-accelerated 2D canvas draws some CSS gradients in an html5 frame as a solid fill. On one edit, a 28 px
repeating-linear-gradienthatch came out flat grey on 44 of 374 frames. Firefox's software canvas draws them correctly.willReadFrequently: trueasks for a canvas that reads back cheaply, which in Firefox means software, so the canvas each frame is drawn on now requests it.It cost nothing measurable. Firefox and Chrome baked in the same time with and without it, and Safari drew frames in about 25 ms either way. The drawing version goes to 2, so bakes cached with flat gradients are redrawn.
Verify:
npm run verify:ci. Then, in a windowed Firefox, bake an html5 clip with a finerepeating-linear-gradient: the frames show its stripes. Headless Firefox draws in software unless its GPU canvas is forced on, so the bug doesn't show there.Merge after #279. Its drawing version is what this raises.
Merge bottom-up: #280 targets #279's branch, and moves to
mainonce #279 lands.