Skip to content

parseFragment / parseSVGFragment should use custom renderer #2876

Open
@nolanlawson

Description

@nolanlawson

As noted here (#2781 (comment)), we should consider parseFragment and parseSVGFragment to always be "risky." In this way, they should always go through the "custom" renderer rather than the bare-metal renderer.

We didn't do this in #2781 to avoid holding up that PR, but we should do this.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions