w3c / w3c/element-timing

Should SVG be supported?

Open
#56 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
61
Forks
19
Avg merge
1d 10h
Merged PRs (30d)
1

Description

Currently we only support image elements inside SVG, but SVG can have other things. It would be good to think about whether we need to provide more support for SVG. To provide support we'd need to know at least:

  • How to compute the intrinsic size of the SVG? Not sure if this is well-defined for SVGs, as I don't think we could just use their declared size.
  • What timestamp(s) to expose. Is render time after load still good enough here?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the issue's open questions about SVG intrinsic size and which timestamps to expose. Done means reaching a clear decision on whether to support non-image SVG content and defining the required sizing and timing behavior.

Written by the indexing model from the issue text.

Assessment

Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.