- 03 Jan, 2016 3 commits
- 02 Jan, 2016 22 commits
-
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
Felix Epp authored
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.
-
Karel Bilek authored
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
Part of the MessageDetailView // FREEBIE
-
lilia authored
Also refactor generic error view to make this simpler. // FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
- 01 Jan, 2016 1 commit
-
-
lilia authored
Fixes #559 https://url.spec.whatwg.org/#url-code-points // FREEBIE
-
- 26 Dec, 2015 1 commit
-
- 22 Dec, 2015 3 commits
- 21 Dec, 2015 7 commits
-
-
David Baldwynn authored
-
David Baldwynn authored
-
lilia authored
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
-
lilia authored
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
-
lilia authored
closes #529 // FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
Fixes #534 // FREEBIE
-
- 18 Dec, 2015 3 commits
-
-
lilia authored
// FREEBIE
-
lilia authored
// FREEBIE
-
lilia authored
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
-