guardian / guardian/fence

window.location

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Some scripts use information `window.location` to decide how to execute (i.e. what protocol to load dynamic scripts over). In `srcdoc`, this information is not provided.

Contributor guide

No contributing guide indexed for this repository

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 tracing how the project creates or runs code in srcdoc and where scripts read window.location. Determine the expected protocol information for dynamic script loading, then add coverage showing the intended behavior when location is unavailable. Done means scripts can make the required protocol decision in srcdoc.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.