From fb5240aabd67a6a6f07d85b5f003c757e38b95dd Mon Sep 17 00:00:00 2001
From: Matthew Hodgson <matthew@matrix.org>
Date: Wed, 23 May 2018 14:00:54 +0100
Subject: [PATCH] explain why we're now including <p/>s

---
 src/Markdown.js | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/src/Markdown.js b/src/Markdown.js
index e02118397b..9d9a8621c9 100644
--- a/src/Markdown.js
+++ b/src/Markdown.js
@@ -102,6 +102,15 @@ export default class Markdown {
             // (https://github.com/vector-im/riot-web/issues/3154)
             softbreak: '<br />',
         });
+
+        // Trying to strip out the wrapping <p/> causes a lot more complication
+        // than it's worth, i think.  For instance, this code will go and strip
+        // out any <p/> tag (no matter where it is in the tree) which doesn't
+        // contain \n's.
+        // On the flip side, <p/>s are quite opionated and restricted on where
+        // you can nest them.
+        //
+        // Let's try sending with <p/>s anyway for now, though.
 /*        
         const real_paragraph = renderer.paragraph;