Skip to content

Make <canvas> optional #126

Description

@steren

For this use case:

Composing HTML Elements with Effects. A limited set of CSS effects, such as filters, backdrop-filter, and mix-blend-mode are already available, but there is a desire to use general WebGL shaders with HTML.

I wouldn't expect the need to introduce any <canvas> in the DOM to achieve that. Semantically, styling the page shouldn't require inserting any additional element.

Can we imagine a version of html in canvas that is enabled via CSS< and not by wrapping the page within a <canvas>? What if one CSS attribute could mean "Use general WebGL shaders with HTML"

To some extent, I was expecting this kind of UI innovation to come from CSS Houdini. But I have always been frustrated with Houdini that I just couldn't just get the webGL context (or even do animations).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions