v3.6.0 - html-in-canvas engine added to core

[tinchox5]

Features

• engine: ship html-in-canvas in the default build, with a guide 8294802
• stream: add animations: false to stop following running animations 932df5e

Full Changelog: v3.5.0...v3.6.0

---

This discussion was created from the release v3.6.0.

[tinchox5]

Chrome 157, rolling out now, ships html-in-canvas: the browser paints a DOM element into a canvas by itself. SnapDOM 3.6.0 can use it as a second engine:

import { snapdom } from '@zumer/snapdom'

const result = await snapdom(el, { engine: 'html-in-canvas' })
const png = await result.toPng()

Where the API is missing (Firefox, Safari, older Chrome), SnapDOM falls back to the SVG engine on its own and returns the same result, so you can set the option everywhere.

SVG stays the default because it is faster. Try html-in-canvas when native form controls or scrollbars have to look exactly like the page.

• Live demo: https://snapdom.dev/labs/html-in-canvas/
• How-to: https://snapdom.dev/how-to/html-in-canvas/

npm i @zumer/snapdom@latest

---

SnapDOM 3.6.0：新增第二个渲染引擎 html-in-canvas

Chrome 157 正在陆续推送，带来了 html-in-canvas：浏览器可以自己把 DOM 元素绘制到 canvas 中。SnapDOM 3.6.0 可以把它作为第二个引擎使用：

import { snapdom } from '@zumer/snapdom'

const result = await snapdom(el, { engine: 'html-in-canvas' })
const png = await result.toPng()

在没有这个 API 的浏览器中（Firefox、Safari、旧版 Chrome），SnapDOM 会自动回退到 SVG 引擎，返回同样的结果，所以可以在所有环境中直接开启这个选项。

默认仍然是 SVG 引擎，因为它更快。当原生表单控件或滚动条需要和页面完全一致时，可以试试 html-in-canvas。

• 在线演示：https://snapdom.dev/labs/html-in-canvas/
• 使用指南：https://snapdom.dev/how-to/html-in-canvas/

npm i @zumer/snapdom@latest