mathiasbynens / mathiasbynens/jsperf.com
400 Bad Request in Chrome (but not with Firefox)
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 471
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
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
The issue provides only a screenshot and reports a 400 response in Chrome but not Firefox. Start by reproducing the request in both browsers and comparing their network details; done means identifying the cause and confirming the affected request succeeds consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100