Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderThis bit was interesting. bool Quirks::requiresUserGestureToPauseInPictureInPicture() const { #if ENABLE(VIDEO_PRESENTATION_MODE) // Facebook, Twitter, and Reddit will naively pause a <video> element that has scrolled out of the viewport, // regardless of whether that element is currently in PiP mode. // We should remove the quirk once <rdar://problem/67273166>, <rdar://problem/73369869>, and <rdar://problem/80645747> have been fixed. if (!needsQuirks()) return false; if…
If I'm understanding L958+ [1] There's a hyper specific css class browser quirk because the login button for gizmodo/kotaku/etc's CMS's svg icon click event wasn't firing... and here I am fixing my day-to-day browser bugs like a chump [1] https://github.com/WebKit/WebKit/blob/main/Source/WebCore/pa...
It was eye opening for me when I learned that browsers have domain specific hacks to help them work sometimes.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 400
- Total comments
- 179
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2021-02-17 | WebKit QuirksFirst breakout | momonga | 196 | 87 |
| 2022-10-14 | WebKit Quirks.cppBest thread · Latest 20+ point return | Bodacious1445 | 199 | 91 |
| 2024-10-23 | WebKit Quirks | OuterVale | 3 | 0 |
| 2025-01-14 | WebKit Quirks | darknavi | 2 | 1 |