Add test for Intl.Locale from "und"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
Browsers don't behave consistently. See https://github.com/keymanapp/keyman/issues/13610
A test should be added asserting the behavior of new Intl.Locale("und").
Whoever takes this issue should independently verify what the expected behavior should be in the spec of the following functions:
let locale = new Intl.Locale("und");
assert.sameValue(locale.language, "???")
assert.sameValue(locale.script, "???")
assert.sameValue(locale.region, "???")
assert.sameValue(locale.toString(), "???")
CC @srl295
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
Start with the ECMAScript specification for Intl.Locale and determine the expected values for language, script, region, and toString() when constructed with "und". Then locate the appropriate Intl.Locale test entry point in test262 and add assertions for those values; done means the test reflects the specification and covers all four properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- internationalization, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100