The Invisible Shape
Comments on “The Invisible Shape”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
The essay traces the history and usability problems of hierarchical context menus, from Xerox PARC's 1976 Smalltalk-76 pop-up menus to Apple's 1987 sub-menus, and explains why diagonal cursor movement to sub-menus is fragile.
Why it ranked
No. 24 of 106 with a score of 0.61. The panel rated it highest on new information (0.91) and technical depth (0.82), lowest on significance (0.40). Placed No. 24, No. 50 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Well-researched, substantiated history and technical survey of context-menu safe-triangle techniques; practical for UI builders, though niche in scope and not a major industry development.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed, code-backed exploration of submenu pointer-intent algorithms, their history, tradeoffs, accessibility implications, and implementation patterns. It is highly useful to UI engineers, though its importance is concentrated in interface development rather than broad technology.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.61total under rubric v2.3
- Significance0.40
- Reader interest0.65
- Audience breadth0.55
- Practical relevance0.76
- Substantiated0.76
- Technical depth0.82
- New information0.91
- Counts against: Promotional0.03
- Counts against: Overclaim0.12
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.48 | 0.25 | 0.48 | 0.40 | 0.23 | +0.24 | +0.097 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.55 | 0.60 | 0.80 | 0.65 | 0.25 | +0.26 | +0.169 |
| Audience breadthHow many people who build technology does it concern? | 0.72 | 0.45 | 0.48 | 0.55 | 0.27 | +0.13 | +0.072 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.91 | 0.60 | 0.76 | 0.76 | 0.31 | +0.22 | +0.166 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.76 | 0.70 | 0.82 | 0.76 | 0.12 | +0.05 | +0.038 |
| Technical depthHow technically substantive is it? | 0.98 | 0.70 | 0.78 | 0.82 | 0.28 | +0.05 | +0.041 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.90 | 0.93 | 0.91 | 0.03 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.05 | 0.01 | 0.03 | 0.04 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.19 | 0.10 | 0.08 | 0.12 | 0.11 | −0.11 | −0.014 |
| Sum of contributions | +0.608 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.608 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-12/24/"><img src="https://rubric.hrih.si/badge/2026-11-12/24.svg" alt="Ranked #24 on Rubric, 12 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 5 matches source · 1 no source given · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceDate
The Amazon menu patent US9733783B1 was filed on November 1, 2012, four months before Ben Kamens's post.
The cited source says the same thing.
The article says “Their patent, US9733783B1, was filed on November 1, 2012. Four months before Ben's post”
The source says “Filing date 2012-11-01”
Source cited by the article: patents.google.com/patent/US9733783B1/en
Couldn’t checkCausal conclusion
Michael, Gareth Farrington and Drew Stamps built the Amazon mega dropdown menu.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Michael, Gareth Farrington and Drew Stamps built that menu at Amazon”
The source says No passage could be compared.
Source cited by the article: patents.google.com/patent/US9733783B1/en
Matches sourceNumber
The Amazon patent describes three triangles and a circle: a main triangle, two additional triangles above and below, and a small circle around the cursor.
The cited source says the same thing.
The article says “And the patent doesn't draw one triangle. It draws three triangles and a circle”
The source says “the enlarged region comprises a first triangular region 316 , a second triangular region 319 , a third triangular region 323 , and a circular region 324”
Source cited by the article: patents.google.com/patent/US9733783B1/en
Matches sourceCausal conclusion
Adobe's React Aria team tried the safe-area DOM element approach and dropped it because the element re-renders on every mouse move and a fast flick can get ahead of it.
The cited source says the same thing.
The article says “Adobe's React Aria team tried this approach and dropped it for exactly that reason”
The source says “We originally considered this approach but found it to be less reliable when moving your pointer more quickly than the triangle can get re-rendered”
Source cited by the article: react-aria.adobe.com/blog/creating-a-pointer-friendly-submenu-experience
Couldn’t checkDate
In 2013 Ben Kamens investigated how fast Amazon's Shop by Department menu felt and explained that it checks whether the cursor moves inside a triangle toward the sub-menu corners.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “In 2013 he got nerd sniped by how fast Amazon's "Shop by Department" menu felt, and figured out why”
The source says No passage could be compared.
Source cited by the article: bjk5.com/post/44698559168/breaking-down-amazons-mega-dropdown
No source givenNumber
Base UI uses a cursor speed threshold of 0.1 px/ms plus a 40ms timer for a stopped cursor.
The article gives no link or citation for it.
The article says “Base UI checks how fast you're moving (and still keeps a tiny 40ms timer for a hand that stops”
The source says No source to compare with.
Matches sourceNumber
React Aria compares angles with Math.atan2, uses a longer timeout instead of a speed check because of motor impairments, widens the allowed angle by 15°, and closes only after two wrong movements in a row.
The cited source says the same thing.
The article says “widen the allowed angle by 15° on the top and bottom”
The source says “We added 15 degrees of tolerance to the top and bottom angles”
Source cited by the article: react-aria.adobe.com/blog/creating-a-pointer-friendly-submenu-experience
Matches sourceGeneralization
On macOS the safe triangle only protects movement into the sub-menu; when returning to the parent menu, the rows light up right away.
The cited source says the same thing.
The article says “The triangle only works one way. It protects you on the way into the sub-menu, but when you come back to the parent menu it's gone”
The source says “Notice how the safe triangle works when moving from a top-level menu to a nested menu but not when returning from the nested menu to the top-level menu”
Source cited by the article: smashingmagazine.com/2023/08/better-context-menus-safe-triangles
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 12 Nov 2026, 05:47 UTC. It played no part in the ranking.