Service workers allow for more responses to be executed as script
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Before service workers you could only execute as script what <script src> allows you to target. After service workers any response a service worker can obtain, can be given to a <script>. E.g., consider a response to a request whose method is POST or one that has a custom Accept header value.
Should we enshrine this as another weakening of the same-origin policy or do something about it?
Credit: 1lastBr3ath.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the service-worker response behavior and its interaction with script requests described here, then determine whether the specification should document the behavior or change it. Done requires an explicit resolution of that design question.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100