This is a translation of commit 363134d28cb7ff8d2313278e1b4b6c09b5bf9bed
from CoffeeScript to JavaScript. Original commit message from
363134d28cb7ff8d2313278e1b4b6c09b5bf9bed:

When saving a draft to the drafts store, don't save changes for fields
which aren't actually set. This prevents us from accidentally later
restoring `null` to one of these fields.

Fixes an issue where creating an annotation when logged-out would result
in a null permissions field.

These were lost when translating annotation-test.coffee ->
annotation-test.js using the `coffee` command.

Tidy up the CoffeeScript-generated code in annotation-test.js.

These were lost when translate annotation.coffee to annotation.js using
the `coffee` command.

Tidy up the CoffeeScript-generated code in annotation.js.

annotation-test.js is just the output from `coffee -c ...` untouched.

directive/annotation.js is just the output from `coffee -c ...`,
untouched.

This is horrible, but while we're migrating this page to the app, this
is the quickest and easiest fix for the homepage typeface.

Remove Font Awesome and move add missing social media icons to H icon font

Font Awesome was used for the 4 icons on the homepage

 - Twitter, GitHub, RSS feed in the footer
 - 'Drag' icon in the bookmarklet installation instructions

Reduce page weight and simplify our lives by having all the icons
in a single icon font.

Validate incoming annotation data with jsonschema

Handle missing permissions on annotations more gracefully

Don't save null permissions/tags/text to drafts store

Ensure old sort control isn't shown in sidebar

When saving a draft to the drafts store, don't save changes for fields
which aren't actually set. This prevents us from accidentally later
restoring `null` to one of these fields.

Fixes an issue where creating an annotation when logged-out would result
in a null permissions field.

a055f4c inadvertently re-enabled showing the old annotation sort control
in the sidebar, as a result of the one remaining use of the ambiguous
"isStream" variable.

This commit ensures that "isStream" is only ever set on the actual
stream page, and not in the sidebar.

Fixes #2750.

Fix a font size on the front page

Move front page from WordPress into app

Keyboard focus the login form when shown

Automatically put the keyboard focus on the username field in the login
form when it's shown.

Fix sending of WebSocket messages enqueued during a disconnection

Any WebSocket messages submitted whilst the WS is disconnected
should be re-sent when the WS reconnects.

This was broken because upon a disconnect, the 'onclose'
event handler first synchronously called reconnect(), resulting
in a new WebSocket instance being created and then set 'socket'
to null. This caused an error in sendMessages() after the 'onopen'
event was triggered.

Fix the problem by not using a null 'socket' var to represent
a disconnected socket. Instead just use the WebSocket's readyState
property.

Also reduce these to just the one 152x152 icon instead of several
different ones. This should be sufficient. The tiny downside is that
older devices download the larger image and then rescale it.

This just copies the already compiled and minified main.css file into
the app, doesn't yet try to copy the source Sass files and recreate the
assets pipeline for them.

This uses a completely separate front_css webassets bundle for now, the
CSS for the front page should be integrated with that in the site_css
bundle later.

Remove unused `deleted` property handling

At some point in the distant past (7f36f3a) annotation deletes were
handled by adding the "deleted" property to annotations and anonymising
them. Now we actually delete them.

This commit removes code that was intended to handle such annotations.

Remove "show_unanchored_annotations" feature

We've discussed this feature and decided that it can't be turned on in
its current state. This commit removes it.

Note that the feature flag in `h/features.py` remains until these
changes are deployed out to production.

Merge pull request #2739 from hypothesis/trello-177-change-the-default-behavior-of-the-embed-to-highlights-on-by-default

Enable highlights by default everywhere

Fix the missing threads in the stream

This reverts commit 5a5b4e345c050a71e619fb5732426b2306f29e64.

Add a new, undocumented separate_replies=True option to the search API.

If separate_replies=True option is _not_ given to the search API, then
it reverts to its previous behaviour: _do_ include replies in the "rows"
list returned. This is the same behaviour that the search API had befor:
it returns both top-level annotations and replies in the one "rows"
list, but without any guarantee that if some annotations/replies from a
given thread are in the list then all annotations/replies from that
thread will be in it.

If separate_replies=True _is_ given then the API follows the new
behaviour: "rows" contains top-level annotations only, and a separate
"replies" list containing all replies to the annotations in rows is also
inserted into the result.

Do the concatenating of these loadAnnotations() instead of in multiple
places that call it.

Fixes #1916.

Get rid of "Message not found" messages on the /stream page.

Problem:

The stream requests the most recent n annotations from the
search API, but what it actually gets is the most recent n annotations
_and replies_. In some cases a reply may be in this set while the parent
annotation that it is a reply to is not.  When that happens, the frontend
just displays "Message not found" in place of this thread (parent
annotation and replies).

Solution:

Change the semantics of the search API: only return the top-level
annotations (not reply annotations) in "rows". Replies are always
filtered out from the Elasticsearch query results. "total" (and "limit" and
"offset") only apply to these top-level annotations.

Additionally, always do a second Elasticsearch query to get _all_ reply
annotations to the matching top-level annotations, and return these in a
new "replies" key in the API response.

This means that whenever the frontend calls the search API, it always
gets back all of the replies to all of the annotations that it gets, so
it always has the complete threads and feeds them all into the threading
code, which can safely assume that it has the complete threads and no
longer produces any "Message not found" messages.