Implementation tracking
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start by reviewing the linked WebKit, Bugzilla, Chromium, Kiesel, and QuickJS NG engine reports to verify their current implementation status. Update the checklist and links with any confirmed changes; the work is done when each listed engine's support status is current and traceable to its issue or release.
Written by the indexing model from the issue text.
Description
Major Browsers
- JSC / Safari: JSC behind
--useIteratorIncludes=1 - SpiderMonkey / Firefox: Enabled by default in Firefox 154
- V8 / Chrome: Nightly behind
--js-iterator-includes
Other Engines
- Kiesel: Enabled by default in nightly
- QuickJS NG: Enabled by default in 0.16.0
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·