Vals-Smith

/ palantir / blueprint

PUBLIC

Updated 7/19/2026

A React-based UI toolkit for the web

58 Branches 12480 Commits 312 Contributors 59 Tasks

Key Takeaways

Cost / Test vs. Accuracy

Claude Fable 5 leads at 93.22% for $5.33 per test, while GPT-5.6 Terra reaches 88.14% for $0.49 per test.

Latency vs. Accuracy

GPT-5.6 Terra is the fastest model in the 52-of-59 tier at 526 seconds; Claude Fable 5 takes 754 seconds for three additional resolved tasks.

Average token use / test

Input
Output
Reasoning
Cache read
Cache write
Claude Sonnet 5
8.1M
Claude Opus 4.7
4.0M
Claude Opus 4.8
3.5M
Claude Fable 5
2.6M
GLM 5.2
2.4M
Gemini 3.5 Flash
2.2M
Kimi K3
1.8M
GPT-5.6 Luna
1.4M
GPT-5.6 Sol
1.4M
GPT 5.5
1.4M
Claude Haiku 4.5 (Nonthinking)
1.4M
Muse Spark 1.1
1.1M
Grok 4.5
647K
Gemini 3.1 Pro Preview (02/26)
601K
GPT-5.6 Terra
598K

Tasks with failures

PassedFailed
Model051361b08c037613866c7147cbe324a48433c780bc42a0c1a4587c0a4c88a056273c37632fbab8d59758956f23bb6310ceb80e9b7b90ef52b9adf0ac56b2a8c5e8bdcc791bdccc283b0d51c90cdc7c104e15084fe7d418ef46419e
Claude Fable 5
GPT-5.6 Terra
GLM 5.2
Claude Opus 4.7
Claude Opus 4.8
GPT-5.6 Luna
Grok 4.5
Claude Sonnet 5
Kimi K3
Gemini 3.5 Flash
GPT 5.5
GPT-5.6 Sol
Muse Spark 1.1
Gemini 3.1 Pro Preview (02/26)
Claude Haiku 4.5 (Nonthinking)

Task detail

051361b08429

Issue statement

DateRangeInput does not close its calendar popover when Escape is pressed

The DateRangeInput component (in @blueprintjs/datetime) opens a calendar popover when one of its two text inputs is focused. Standard overlay/popover behavior in the toolkit is that pressing the Escape key while interacting with the control dismisses the popover, but DateRangeInput ignores the Escape key entirely.

Steps to reproduce

  1. Render a DateRangeInput and focus the start input so the calendar popover opens (isOpen becomes true).
  2. Press the Escape key while the input is focused.

Expected behavior

Pressing Escape should close the popover (isOpen becomes false) and the input fields should no longer be focused.

Actual behavior

Nothing happens: the popover stays open and the input keeps focus.

The key-down handling for the range inputs should treat Escape as a request to dismiss the popover and blur the currently focused field.

Hidden tests
diff --git a/packages/datetime/test/components/dateRangeInputTests.tsx b/packages/datetime/test/components/dateRangeInputTests.tsxindex deb4c7210..018d4aeca 100644--- a/packages/datetime/test/components/dateRangeInputTests.tsx+++ b/packages/datetime/test/components/dateRangeInputTests.tsx@@ -602,6 +602,21 @@ describe("<DateRangeInput>", () => {             expect(root.state("isOpen"), "popover closed at end").to.be.false;         }); +        it("pressing Escape closes the popover", () => {+            const { root } = wrap(<DateRangeInput {...DATE_FORMAT} value={[null, null]} />);+            root.setState({ isOpen: true });++            const startInput = getStartInput(root);+            startInput.simulate("focus");++            expect(root.state("isOpen")).to.be.true;++            startInput.simulate("keydown", { key: "Escape" });++            expect(root.state("isOpen")).to.be.false;+            expect(isStartInputFocused(root)).to.be.false;+        });+         it("Clicking a date invokes onChange with the new date range and updates the input fields", () => {             const defaultValue = [START_DATE, null] as DateRange;  

Head-to-head

VS

Accuracy

93.22%Δ 5.08%

88.14%

Cost / test

$5.33

$0.49Δ $4.84

Latency

754s

526sΔ 229s

Cost distribution

$0.00$8.67$17.35

Latency distribution

0s1097s2194s

Input token distribution

0159.5K319.0K

Output token distribution

054.6K109.2K

Task outcomes

59 tasks

Both
A only
B only
Neither