Site Logo: Correct evaluation of the Display Header Text checkbox in Customizer preview.
Fonts: change path to look for the svg in the right directory

Reported here:
https://wordpress.org/support/topic/error-500-568
Merge pull request #1281 from jeherve/fix/path-jetpack-font

Fonts: change path to look for the svg in the right directory
Changed the default TED lang parameter

The previously used eng string broke the embed
and made some unit tests fail. Replacing it with
en fixes those problems.
Shortcodes: update Ted Shortcode examples as well

See a382a105594c328cbbfad705457595da4a189234
Update unit tests for concat css.

Previously it tested to make sure we were de-enqueueing the asset —
which is wrong.  We fixed it to just short circuit the output, instead.
 Unit tests need to catch up.
Gallery Widget: add default slideshow background color setting

This fixes a notice when WP_DEBUG was set to true
REST: Add show_on_front option to site optionss

Merges r108639-wpcom.
REST: Add post title to parent post ref on post objects

Merges r108702-wpcom.
contact form: RTL support for the form editor, fixes #6840

See https://github.com/Automattic/jetpack/pull/1261

Merges r108236-wpcom.
Contact form RTL: use tahoma by default

See https://[private link]?topic_id=547539

Merges r108437-wpcom.
Merge commit '6246b18'
REST API: allow the returned HTTP code to be changed from 200 for successful actions.

This change is implemented because upcoming endpoints for site import/exports need to return a HTTP 202 response.

Props to @mdawaffe for the patch. :)
See https://[private link]

Merges r107424-wpcom.
REST API: move the CORS/preflight action to fire before authentication is processed.

Firefox does not pass authorization headers when executing OPTIONS/preflight requests whereas other browsers do. Apparently (http://stackoverflow.com/a/15734032) this is actually in par with the spec, though there's an effort to change the spec. Because the authorization headers are not passed in, some requests would fail at the authentication process and thus not return the preflight headers. I believe that the problem was amplified in production where prefork kicks in.

This simply moves the actions associated with the preflight headers to fire before authentication is verified. I've also added some tests for preflight requests since we didn't have any. However these tests don't cover browser inconsitencies like this one.

see https://[private link]

Merges r107759-wpcom.
revert [107759] as it didn't solve the problem with CORS and firefox

Merges r107760-wpcom.
REST API: adjustments to CORS/preflight

* Move the action to fire before authentication is processed. Authentication shouldn't be necessery for the preflight requests. Originally deployed in [107759] but later reverted.
* Explicitly output with a 200 status for preflight requests

This is an attempt to fix a production/firefox specific issue. However even if it doesn't fix the issue, these improvements still make sense as they do not cause any regressions and make the output a bit cleaner for these requests.
see https://[private link]

Merges r108139-wpcom.
Merge commit '1a1c163'
Store: REST API: Adding a cart_item definition to the API documentation and using it for the shopping cart endpoint.

Part of https://[private link]

Merges r107784-wpcom.
REST API: /me/posts endpoint. Return the Jetpack author.

We were returning the wpcom user data instead of returning the Jetpack author data stored on post_meta for jetpack sites.

See:
https://github.com/Automattic/calypso-pre-oss/issues/1465
https://[private link]#comment-618

Merges r108070-wpcom.
REST API: /me/posts Endpoint: Improve readability of r108070

See: https://a8c.slack.com/archives/api/p1415109581000761

Merges r108079-wpcom.