…These labels should be Confidence and Accuracy.
words/URLs in predictions and comments from spilling all over the page.
if a another URL component is included (& character). Apply the same fix in another place just to be safe.
plaintext URLs to "url":url for RedCloth. This fixes tricycle/predictionbook#4
fix (debounce, use async XHR, also check on page load)
the "When will you know?" value. This avoids making a ton of requests.
browsers (at least Firefox) automatically fill in the last value on page reload.
server response is not stale (due to the text box being changed during the request). This fixes the lying.
instead of a vague "N months" or "N years" string.
because that looks like the "3 days" is part of the prediction. This can get a bit confusing, so change it to "<prediction> TBD in 3 days" (TBD = to be decided/judged).
the responses <ul> on prediction page; minor margin/padding tweaks
based on the numerical value. This makes them easier to tease apart from the textual noise.
…more obvious that this is the right place to record your opinion
up new users, who think that it's the right place to record their opinion.
* Remove "NN% against" display logic, just show the raw confidence everywhere. Users will finally stop typing the wrong number into the percent box (an irrevocable mistake!) * Say "What's your estimate of this happening?" instead of "How sure are you?". This is less confusing in the case of being strongly against the prediction; the updated phrasing should help out new users.