METHODS / RESULTS / LIMITS
How MouseCheck results work.
Use this reference to choose a test, decode its named result and repeat it under a controlled condition.
MouseCheck reports a signal delivered to this browser, a context you declare, or a calculation from values you enter. None of those is automatic access to mouse firmware, an internal switch or the USB report stream.
START WITH THE QUESTION
Nine routes. Nine different outputs.
A broader number is not a better answer. Choose the page whose input and endpoint match the decision you need to make.
Signals in this browser
- Complete mouse testDid movement, main/secondary presses and both wheel directions reach this test area?Event presence · not device health
- Double-click testDid separate intended presses repeat, go missing or complete—and did the browser recognize an intentional primary double?Declared actions · not switch wear
- Scroll wheel testDid declared down and up phases stay internally consistent and separate as opposite sign groups?Wheel events · not physical detents
Measurements and settings
- Movement-rate testHow often did accepted movement samples arrive in one controlled five-second browser round?Browser sample estimate · not USB polling certification
- Mouse latency methodsWhich endpoints and equipment fit browser response, mouse-only or click-to-display latency?Method choice + bounded browser check
- DPI lookup guideIs the value configured, an identified onboard stage, a browser estimate or only OS pointer speed?Source qualification · not firmware inspection
- Sensitivity converterWhich target setting keeps calculated horizontal turn distance similar under named assumptions?Transparent starting value · not verified feel
Troubleshooting after a result
- Double-click troubleshootingWhich comparison follows a repeat, matching-count, missing/hold or recognition result?Evidence scope · internal cause unidentified
- Scroll-wheel troubleshootingDoes the next check belong to browser signal, page behavior, app settings or device scope?Observation + context · not encoder diagnosis
READ THE EVIDENCE AT ITS LEVEL
A result cannot silently climb this ladder.
- 1
OBSERVED
Browser signal
An event, timestamp, delta, unit or count delivered to this page. - 2
DECLARED
Your physical action and context
The button, direction, input type, app, connection or setting you report. - 3
CALCULATED
Rule-based result
A named status, median, rate estimate, formula output or deterministic next-check path. - ?
NOT IDENTIFIED
Internal hardware cause
Requires a separate physical, electrical, USB or display endpoint. The browser result does not supply it.
Example: one opposite wheel event is observed. “I rolled down only” is declared. “Unexpected direction change” is calculated. “Worn encoder” is still not identified.
RESULT DICTIONARY
Find the completion rule before trusting the label.
These are MouseCheck’s current product rules. Site-defined minimums and comparison bands are disclosed; they are not presented as universal hardware standards.
| Result family | Complete when | Allowed conclusion | Next action |
|---|---|---|---|
| Basic input: Normal / Does not meet / Not checked | Movement, main, secondary and both vertical wheel signs are resolved in one round. | Required signals did or did not reach this browser check under the named condition. | Return to the complete test or choose the symptom-specific page. |
| Unwanted repeat / Missing input / No repeat observed | The declared separate-press plan is stopped cleanly and downs/completions can be compared. | The selected button produced matching, extra or incomplete browser actions in that round. | Choose the double-click next check. |
| Scroll consistent / Reversal / Same-sign phases / Not enough input | Down and up phases are stopped; each needs eight vertical events for a complete consistency comparison. | Browser event signs stayed consistent, changed inside a phase, failed to separate or were insufficient. | Choose the scroll next check. |
| Approximate browser movement sample rate / No estimate | Five seconds finish with at least 20 usable short gaps whose duration totals at least 3,000 ms. | An approximate browser-observed sample rate and closest standard comparison band, or why no estimate exists. | Repeat the same motion after changing one condition; use hardware tools for USB report rate. |
| Browser click-response round | Ten trusted main-button samples finish in the fixed target without focus interruption. | Median/P95 browser event age and event-to-first-rAF callback timing for that tab and round. | Use the guide’s physical/USB/display protocol for a mouse-only or click-to-light question. |
| Configured DPI / Documented stage / Estimate / Not DPI / Unknown | The source, value and active-stage evidence are declared where applicable. | Whether a value is usable as configured DPI, only an estimate, an OS setting or still unknown. | Use a qualified number in the converter, or keep it unknown. |
| Sensitivity starting value / Measured correction | Positive source/target values and a supported/reference or custom linear yaw are provided. | A calculated horizontal hip-fire starting setting under shown assumptions. | Test one slow full turn in the target mode and correct from measured distance if needed. |
| Troubleshooting next-check plan | Required observation/context fields are selected. | A deterministic comparison path based only on those declarations. | Perform the three actions in order; internal cause remains unidentified. |
EXACT METHODS BY FAMILY
Inputs, completion rules, outputs and boundaries.
Open the family that matches your result. The compact field strip gives the contract; the notes explain the calculation or event rule.
Complete browser mouse check
Which basic mouse signals reached one test area?
- Required: mouse movement, main-button down, secondary-button down, positive vertical wheel delta and negative vertical wheel delta.
- “Tried, no signal” records the visitor’s attempt and prevents a Normal result while no matching event arrives.
- Middle, drag, browser `dblclick`, horizontal wheel and side buttons are optional evidence. Back/Forward zero is inconclusive because a browser may navigate before the page receives an event.
- Release changes held state; a completed drag needs at least 24 CSS pixels and release inside the area. Ctrl-modified zoom-style wheel input is excluded.
A Normal result means this round met the published five-signal browser rule. It does not rule out an intermittent problem or inspect physical parts.
Separate unintended repeat from intentional double-click recognition
Two tasks share one page but keep independent conclusions.
Unwanted-repeat round
- Default plan: 20 separate physical presses; visitor may choose 5–100.
- Main completion is native `click`; right/middle completion is a matching in-area release.
- More selected-button downs than declared, or a native main `dblclick` during the single-press protocol, is repeat evidence. Fewer downs/completions is missing or incomplete input.
- Right/middle completed pairs with down gaps ≤500 ms are a non-overlapping pace note only; they do not decide the verdict.
Intentional recognition
- The separate module listens only for the browser’s native primary-button `dblclick`.
- It shows the latest down-event gap and names recognized, not recognized or insufficient input.
- Operating-system double-click speed can affect recognition; it is not the same as accidental-repeat evidence.
Declare physical direction; observe browser direction
Signal consistency and event density are separate outputs.
Direction protocol
- Each phase’s first nonzero vertical `deltaY` becomes its reference. Later events are same or opposite to that phase reference.
- A complete consistent result needs zero within-phase reversals and opposite reference signs across the two declared physical phases.
- Zero or 1–7 vertical events remain unverified. Eight is MouseCheck’s sampling rule. Each phase keeps at most 200 events; units remain pixel, line or page.
Five-second event-rate sample
The clock begins with the first nonzero vertical event. The page reports vertical events ÷ 5, sign counts and reported units. It does not grade the number, call it polling frequency or add unlike units into distance.
Approximate browser-observed movement samples per second
A controlled sample, not a direct USB report-rate reader.
Collection
- Trusted mouse or unclassified mouse-compatible Pointer Events are accepted; identified touch/pen input is excluded.
- Coalesced children replace their parent when available. A `mousemove` fallback is accepted only when no Pointer Event arrived in the previous 100 ms.
- Only increasing positive gaps ≤100 ms are usable. Longer gaps are pauses. Focus loss discards the round.
approximate samples/s
1,000 ÷ median usable gap in msSynthetic example: 8 ms median → about 125 samples/s.The nearest 125/250/500/1000/2000/4000/8000 Hz band is a MouseCheck comparison label. Same/different selected band is not a quality grade or USB certification. W3C coalesced events ↗
Event age and first animation-frame callback
The endpoint begins after the operating system and browser expose an event.
Browser-clock endpoints
- Event age at the handler =
performance.now() − normalized event.timeStamp. - The second value runs from normalized event timestamp to the first
requestAnimationFramecallback after target state changes. - Epoch-style timestamps are normalized against
performance.timeOrigin; incompatible values fall back to the handler clock and are labelled.
Interpretation
A requestAnimationFrame callback occurs before a paint opportunity; it does not prove completed pixels or photons. Mouse-only latency needs controlled actuation plus USB reports. Click-to-display latency needs synchronized input and visible-light endpoints.
The source decides whether the number is usable
Configured, documented and estimated values are not interchangeable.
A stable browser ruler estimate still does not read the active firmware profile. If stage or source cannot be proved, the correct result remains unknown.
Calculated horizontal hip-fire turn-distance match
A transparent starting value that must be checked in the target mode.
Target settingsource sensitivity × source DPI × source yaw ÷ (target DPI × target yaw)
cm/360914.4 ÷ (DPI × sensitivity × yaw)
Counts/360360 ÷ (sensitivity × yaw)
Measured correctiontested target setting × observed cm/360 ÷ desired cm/360
CS2/Apex 0.022° and VALORANT 0.07° are exposed as reference profiles, not publisher/current-build certified constants. Use Custom only with a documented linear yaw. Verify one slow physical full turn and keep ADS/scopes, acceleration and perceived speed outside this result.
CONTROLLED A/B
A comparison is useful only when the rule stays fixed.
- 1
Freeze
Name the device/input, browser/app, connection, power, profile and intended action.
- 2
Complete
Meet the page’s full stop/sample rule. Do not save an interrupted or insufficient round as normal.
- 3
Preserve
Keep the named result and its evidence, units, sample count and optional note.
- 4
Change one
Alter one app, setting, profile, port, receiver, power condition, device or computer.
- 5
Repeat
Use the same physical action and completion rule under the new condition.
- 6
Stop at the boundary
Report where the pattern follows; do not turn that scope into an unidentified internal cause.
CURRENT PAGE DATA FLOW
What stays in the page, what copies and what remains unknown.
This is the behavior of the current local source. It is not a claim about a future host, edge log, analytics product or provider retention.
| Page family | Current input in the open page | Clear / retain behavior | User-triggered output |
|---|---|---|---|
| Home, double, scroll, movement rate, latency | Bounded event/timestamp lists, counters, declared conditions and up to two saved A/B summaries where offered. | Reset clears the live round; Clear A/B clears saved summaries; reload clears page memory. | Copy or `.txt` download only after its button is pressed. |
| Sensitivity converter | Entered profiles/settings plus calculated result, rounding and optional measured correction. | Editing an input clears the stale result; reload clears the page. | Copy only after pressing Copy result. |
| DPI and troubleshooting guides | Selected declarations, optional short note where offered and the current deterministic result. | Editing, Reset or reload clears the result. No saved A/B. | No copy/download control on these planners. |
| Production hosting | Server, CDN, edge, access logs, analytics and provider processing. | Not established by this local source review. | UNAVAILABLE until the real host/data flow is reviewed. |
VERIFICATION STATUS
Local evidence is not production or hardware proof.
Each current page family has a pre-code research/specification record, a synchronized local build and focused browser acceptance. That establishes the implemented browser behavior under those tests.
LOCAL PASSRule/code alignmentCurrent pages, scripts, formulas, named outcomes and local browser paths.
NOT TESTEDPhysical device matrixActual model/firmware, free-spin, trackpad, Windows/macOS combinations and assistive technology.
UNAVAILABLEProduction and fieldHost logs/data flow, deployment parity, indexing, real-user comprehension and field performance.
REFERENCE BOUNDARY
Use the result within the endpoint that produced it.
These methods do not inspect switches, wheel encoders, mouse firmware, raw USB/wireless reports or the instant a display changes light. A browser movement value is not an automatic reading of mouse DPI. A calculated game setting is not a publisher-certified promise of identical feel. Keep the named condition, completion rule and uncertainty with every result.