mathiasbynens / mathiasbynens/punycode.js
Match browser implementations (e.g. `１`)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 170
- PR merge metrics
- No merged PRs in 30d
Description
@annevk reported this one.
```
[13:19] matjas: you around? saw that １ turns into some Punycode string per http://mothereff.in/punycode but no browser does that, not even Opera
[13:20] matjas: so if that's IDNA2008... well...
```
http://mothereff.in/punycode#%EF%BC%91.com
AFAICT, that’s just the Punycode algorithm doing its thing. I guess browsers normalize the input first?
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 reproducing the linked mothereff.in/punycode example for the fullwidth digit １ and comparing its output with browser implementations. Determine the expected normalization behavior under IDNA2008, then consider the issue complete when punycode.js matches browser handling for this input and related cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100