FA-25349 / Filter interfaces / Member archive

Exponent syntax is rejected even with uppercase exponent markers · case 04

Exponent syntax is rejected even with uppercase exponent markers is violated by the widget projection.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

This bounded numeric editor accepts ASCII signed integers with surrounding spaces, preserving incomplete drafts and disallowing exponent, decimal and non-ASCII forms. This example checks: Exponent syntax is rejected even with uppercase exponent markers.

Why this case matters

Filter-widget state and serialization must preserve user constraints while the view changes.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
contract fixture 0	`{"blank-open": false, "complete-integer": false, "exponent-rejection": false, "fraction-rejection": false, "incomplete-sign": false, "trim-draft": "1E2"}`	`{"blank-open": false, "complete-integer": false, "exponent-rejection": true, "fraction-rejection": false, "incomplete-sign": false, "trim-draft": "1E2"}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.