Skip to content
Signalcrest
Back to feed
stackoverflowweb

Text input stops receiving keyboard events after cancelling beforeunload confirmation in Chrome

Text input bug fix

Steady
Signal score
7
as of 41d ago
Sources
2
agreeing on angular
Trajectory
Too early
needs a few more snapshots

Why this scored 7

every term, weighted
Velocity+1.5 / 40

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+0.0 / 25

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+2.8 / 25

How many independent communities are talking about the same entity

Recency+5.0 / 10

Decays to zero over 14 days

Saturation penalty2.6 / 30

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite6.7

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology

Signal history

7-day window (free)
Not enough history yet — the trend line fills in as snapshots accrue (every 30 min).

Entities

angulargooglechrome
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/so%3A79985588)](https://www.signalcrest.app/topic/so%3A79985588)

Drop this in a README or blog post — it updates automatically as the score moves.