w3c / w3c/element-timing

url getter special cases data: URLs

Open
#64 2 comments 0 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

Why special case data: URLs? Other URLs can be thousands of code points as well...

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

The issue names only the URL getter and the special handling of data: URLs; no file, test, or entry point is provided. First read the surrounding Element Timing specification and its URL-processing rationale, then identify whether the expected outcome is an explanation or a specification change and record the decision clearly.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.