GitLab

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

The user-agent string includes the information needed (OS + Chrome version) and the console.get() function seems just right. The debugLog itself is not manipulated.

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

Part of the MessageDetailView

// FREEBIE

Also refactor generic error view to make this simpler.

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

// FREEBIE

Fixes #559

https://url.spec.whatwg.org/#url-code-points

// FREEBIE

Recompile missed in 093eb001

// FREEBIE

Rather than simply displaying an inactionable error, render a link that
allows the user to save the unsupported attachment.

// FREEBIE

// FREEBIE

// FREEBIE

Only show sent_at for outgoing messages, matching Android.

The received_at timestamp reflects the time a message was saved locally.
It is necessary on both incoming and outgoing messages for sorting
purposes, but can be confusing in the context of an outgoing message
detail view, since users don't think about themselves "receiving" their
own messages, and may even interpret this as the time that a message was
received by their conversation partner's device.

// FREEBIE

Although in practice, these timestamps are often the same, they needn't
be, and when they aren't, we want the sentMessage.timestamp here.

// FREEBIE

closes #529

// FREEBIE

// FREEBIE

Fixes #534

// FREEBIE

// FREEBIE

// FREEBIE

This chrome alarm business is in place to help us wake up and check for
messages when running in the background. Without it, chrome will suspend
our app after a short period of inactivity. Upon waking, if the app
discovers it is not linked, it prompts you to link it. However, if
you've declined registration (i.e., because you already maxed out your
linked device limit, but chrome auto-added the app to another machine),
we should just wait until explicitly launched again.

Fixes #519

// FREEBIE