Skip to content

Add engine version requirements to renderRequirements (Issue#25)#58

Merged
nytamin merged 1 commit intoebu:mainfrom
Richardpwe:feature/issue-25
Apr 15, 2026
Merged

Add engine version requirements to renderRequirements (Issue#25)#58
nytamin merged 1 commit intoebu:mainfrom
Richardpwe:feature/issue-25

Conversation

@Richardpwe
Copy link
Copy Markdown
Contributor

Adds an optional engine property to renderRequirements: a list of requirements for the rendering engine (e.g. CEF, Gecko) with a minimum required version (version.min). min is intentionally defined as a string so different version formats (CEF, Chromium, WebKit, etc.) are supported.

@dvdeurse
Copy link
Copy Markdown
Collaborator

This looks ok to me, but we probably need something similar in the Server API so that Renderers can expose their supported engines.

@Richardpwe
Copy link
Copy Markdown
Contributor Author

That makes sense, I didn't thought about that.
In the current Server API we already have RenderCharacteristics on RendererInfo, which is meant to correspond to the renderRequirements field in the graphic manifest.

To mirror the new renderRequirements.engine[] in the graphics spec, I’d add an
engine?: { type: string; version: { min: string } }[] field to RenderCharacteristics,
so the structure stays 1:1 between manifest and Server API. That would allow control systems to match a graphic’s engine requirements against what a renderer actually supports.

@nytamin nytamin linked an issue Mar 15, 2026 that may be closed by this pull request
@nytamin
Copy link
Copy Markdown
Collaborator

nytamin commented Apr 15, 2026

Note from Working Group 2026-04-15:

No one is against, approved!

@nytamin nytamin merged commit 1c41786 into ebu:main Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rendering engine version

3 participants