invalid protocol in Firefox → `Http.Error` not caught
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 5
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 1
Description
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the linked elm/http issue, since the report names no source file, test, or entry point in gren-lang/browser. Reproduce the invalid-protocol case in Firefox and trace how it is expected to become Http.Error; done means the error is caught consistently with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100