w3c / w3c/FileAPI

Sort out when blob: URLs can be fetched / navigated

Open
#135 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

TPAC2024
Dominant language
HTML
Stars
118
Forks
52
Avg merge
9d 16h
Merged PRs (30d)
1

Description

This is basically to ensure we track https://github.com/whatwg/fetch/issues/666 in this repository as well.

As part of https://github.com/web-platform-tests/wpt/pull/17606 I've found that that when A embeds B, B can navigate itself to a blob URL of B's creation. But if B hands that to A and A navigates B, it does not work when B is cross-origin. So it does seem to depend on the "source browsing context" (which really is a source document) in some manner.

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 Fetch issue 666 and the behavior described in web-platform-tests pull request 17606. Compare self-navigation with navigation handed across origins, then establish the expected blob URL behavior in terms of the source browsing context; the issue is done when that behavior is specified consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
web-dev
Issue type
Bug
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.