Bug 1436346 - Fix broken link to geckodriver README in TraceLogs docs; r?ato draft
authorRaphael Pierzina <rpierzina@mozilla.com>
Wed, 07 Feb 2018 17:09:51 +0100
changeset 752587 815515ebc07e1bbec5a9fde4cf7d66ff7d942ef0
parent 752154 f138690ccafddacd0de5c207f9c8f66be51001aa
push id98306
push userbmo:rpierzina@mozilla.com
push dateThu, 08 Feb 2018 16:23:02 +0000
reviewersato
bugs1436346
milestone60.0a1
Bug 1436346 - Fix broken link to geckodriver README in TraceLogs docs; r?ato MozReview-Commit-ID: DlF61W3fm5o
testing/geckodriver/doc/TraceLogs.md
--- a/testing/geckodriver/doc/TraceLogs.md
+++ b/testing/geckodriver/doc/TraceLogs.md
@@ -72,18 +72,18 @@ enable trace logs for both geckodriver a
 
 The second way of setting the log level is through capabilities.
 geckodriver accepts a Mozila-specific configuration object
 in [`moz:firefoxOptions`].  This JSON Object, which is further
 described in the [README] can hold Firefox-specific configuration,
 such as which Firefox binary to use, additional preferences to set,
 and of course which log level to use.
 
-[`moz:firefoxOptions`]: ../README.md#firefox-capabilities
-[README]: ../README.md
+[`moz:firefoxOptions`]: https://searchfox.org/mozilla-central/source/testing/geckodriver/README.md#firefox-capabilities
+[README]: https://searchfox.org/mozilla-central/source/testing/geckodriver/README.md
 
 Each client has its own way of specifying capabilities, and some clients
 include “helpers” for providing browser-specific configuration.
 It is often advisable to use these helpers instead of encoding the
 JSON Object yourself because it can be difficult to get the exact
 details right, but if you choose to, it should look like this:
 
 	{"moz:firefoxOptions": {"log": {"level": "trace"}}}