Bug 1263761 - Update defaultSearch in core ping docs for custom search engines. r=gfritzsche draft
authorMichael Comella <michael.l.comella@gmail.com>
Mon, 11 Apr 2016 16:18:28 -0700
changeset 349560 0b24048786851b2e0921467d134b084f8aa86265
parent 349534 5b37f138e5bfdb84fe3460dd115ec225933e0f5f
child 518143 c67c7e2c3869dfc4403e4f7cc3f26ce6b53363a2
push id15132
push usermichael.l.comella@gmail.com
push dateMon, 11 Apr 2016 23:19:05 +0000
reviewersgfritzsche
bugs1263761
milestone48.0a1
Bug 1263761 - Update defaultSearch in core ping docs for custom search engines. r=gfritzsche MozReview-Commit-ID: CuISAHVCLnX
toolkit/components/telemetry/docs/core-ping.rst
--- a/toolkit/components/telemetry/docs/core-ping.rst
+++ b/toolkit/components/telemetry/docs/core-ping.rst
@@ -73,16 +73,19 @@ engine from the search plugins (in order
 
 * In the distribution
 * From the localized plugins shipped with the browser
 * The third-party plugins that are installed in the profile directory
 
 If the plugins fail to create a search engine instance, this field is also
 ``null``.
 
+This field can also be ``null`` when a custom search engine is set as the
+default.
+
 profileDate
 ~~~~~~~~~~~
 On Android, this value is created at profile creation time and retrieved or,
 for legacy profiles, taken from the package install time (note: this is not the
 same exact metric as profile creation time but we compromised in favor of ease
 of implementation).
 
 Additionally on Android, this field may be ``null`` in the unlikely event that