* improve a11y of fields, status page, and more
* tweak nav name
* fix community page and tweak text
* don't show pinned statuses heading unless there are pinned statuses
Based on issues I'm seeing on iOS Safari, I'm guessing that my IDB caching is too aggressive and is hitting origin storage limits, which causes IDB transactions in safari to fail silently and never call any transaction callbacks (`onblocked`, `onerror`, `oncomplete`).
This is pretty bad and causes Pinafore to basically just not work unless you clear site data, which we should avoid. 2 weeks was probably unnecessary anyway; in a social network, who cares about content that's 2 weeks old?
* add application (client) name to statuses
fixes another thing in #6
* add domain blocking (#496)
* add domain blocking
fixes another thing from #6
* show "domain blocking" on profile page
* fix stuff
Part of the way to improving #390.
Before this fix, if you recieved a notification while Pinafore was in a background tab, nothing would happen, because most browsers (Edge, Firefox, Chrome) don't run rAF in background tabs. Furthermore, Chrome doesn't run rIC. In this PR we detect if we're in a background tab and then avoid rAF/rIC in that case.
* make tests faster by logging in directly
* downgrade testcafe
* Revert "downgrade testcafe"
This reverts commit 0f78f5ef63f25b6428de2faba476a353a338c695.
* try a delay
* the delay does not do anything
* disable concurrency in testcafe
* make setup script less noisy
* try transparency of 2?
* Revert "the delay does not do anything"
This reverts commit 438b3519a4e0c325e89f0c2a0eff6a7a4ae11ebd.
* try a delay of 400ms
* okay fine delay of 1s
* try concurrency of 4 again
* more attempts to fix test flakiness
* remove testcafe roles entirely
* really remove testcafe roles
* run testcafe in parallel x2
* run testcafe in parallel x4
* fix online/offline forcing in tests
* fix pin test
