From f79326b2d5ecda064aee93b291ac2838d45f6f40 Mon Sep 17 00:00:00 2001
From: Laurent Cozic <laurent@cozic.net>
Date: Mon, 11 Jun 2018 22:10:04 +0100
Subject: [PATCH] Updated website

---
 docs/clipper/index.html | 15 +++++++++++++--
 readme/clipper.md       | 21 ++++++++++++++++++---
 2 files changed, 31 insertions(+), 5 deletions(-)

diff --git a/docs/clipper/index.html b/docs/clipper/index.html
index 9227d5935e..3bd4aca44b 100644
--- a/docs/clipper/index.html
+++ b/docs/clipper/index.html
@@ -246,7 +246,7 @@
 </li>
 </ul>
 </div>
-<h2 id="troubleshooting-the-web-clipper-service">Troubleshooting the web clipper service</h2>
+<h1 id="troubleshooting-the-web-clipper-service">Troubleshooting the web clipper service</h1>
 <p>The web clipper extension and the Joplin application communicates via a service, which is started by the Joplin desktop app.</p>
 <p>However certain things can interfer with this service and prevent it from being accessible or from starting. If something does not work, check the following:</p>
 <ul>
@@ -258,7 +258,8 @@
 </li>
 </ul>
 <p>If none of this work, please report it on the <a href="https://discourse.joplin.cozic.net/">forum</a> or <a href="https://github.com/laurent22/joplin/issues">GitHub issue tracker</a></p>
-<h2 id="debugging-the-extension">Debugging the extension</h2>
+<h1 id="debugging-the-extension">Debugging the extension</h1>
+<h2 id="in-chrome">In Chrome</h2>
 <p>To provide as much information as possible when reporting an issue, you may provide the log from the various Chrome console.</p>
 <p>To do so, first enable developer mode in <a href="chrome://extensions/">chrome://extensions/</a></p>
 <h3 id="debugging-the-popup">Debugging the popup</h3>
@@ -267,6 +268,16 @@
 <p>In <code>chrome://extensions/</code>, click on &quot;Inspect background script&quot;.</p>
 <h3 id="debugging-the-content-script">Debugging the content script</h3>
 <p>Press Ctrl+Shift+I to open the console of the current page.</p>
+<h2 id="in-firefox">In Firefox</h2>
+<ul>
+<li>Open <a href="about:debugging">about:debugging</a> in Firefox.</li>
+<li>Make sure the checkox &quot;Enable add-on debugging&quot; is ticked.</li>
+<li>Scroll down to the Joplin Web Clipper extension.</li>
+<li>Click on &quot;Debugging&quot; - that should open a new console window.</li>
+</ul>
+<p>Also press F12 to open the regular Firefox console (some messages from the Joplin extension can go there too).</p>
+<p>Now use the extension as normal and replicate the bug you&#39;re having.</p>
+<p>Copy and paste the content of both the debugging window and the Firefox console, and post it to the <a href="https://discourse.joplin.cozic.net/">forum</a>.</p>
 
 <script>
 	function stickyHeader() { 
diff --git a/readme/clipper.md b/readme/clipper.md
index 854ebe1322..a388d252da 100644
--- a/readme/clipper.md
+++ b/readme/clipper.md
@@ -1,4 +1,4 @@
-## Troubleshooting the web clipper service
+# Troubleshooting the web clipper service
 
 The web clipper extension and the Joplin application communicates via a service, which is started by the Joplin desktop app.
 
@@ -12,7 +12,9 @@ However certain things can interfer with this service and prevent it from being
 
 If none of this work, please report it on the [forum](https://discourse.joplin.cozic.net/) or [GitHub issue tracker](https://github.com/laurent22/joplin/issues)
 
-## Debugging the extension
+# Debugging the extension
+
+## In Chrome
 
 To provide as much information as possible when reporting an issue, you may provide the log from the various Chrome console.
 
@@ -28,4 +30,17 @@ In `chrome://extensions/`, click on "Inspect background script".
 
 ### Debugging the content script
 
-Press Ctrl+Shift+I to open the console of the current page.
\ No newline at end of file
+Press Ctrl+Shift+I to open the console of the current page.
+
+## In Firefox
+
+- Open [about:debugging](about:debugging) in Firefox.
+- Make sure the checkox "Enable add-on debugging" is ticked.
+- Scroll down to the Joplin Web Clipper extension.
+- Click on "Debugging" - that should open a new console window.
+
+Also press F12 to open the regular Firefox console (some messages from the Joplin extension can go there too).
+
+Now use the extension as normal and replicate the bug you're having.
+
+Copy and paste the content of both the debugging window and the Firefox console, and post it to the [forum](https://discourse.joplin.cozic.net/).
\ No newline at end of file