Unknown value of 0 means "assume slow" but example shows "assume fast"
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
I can image websites progressively enhancing with effects using code such as:
const minCpuLevel = 2;
if (navigator.cpuPerformance > minCpuLevel) {
// add sparkles
}
But for any devices with unknown value of 0, this would not be enabled, unless explicitly tested for.
Should the Unknown special value be some large constant or Number.MAX_SAFE_INTEGER?
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 issue's JavaScript example and the stated unknown value of 0. Resolve whether the unknown value should preserve the example's comparison behavior or use a large sentinel, then align the API specification and examples; done when the unknown-value rule is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100