From 0e3224c52fea7ab24f3c0c5e955870e0e24fed30 Mon Sep 17 00:00:00 2001
From: Peter Cai <peter@typeblog.net>
Date: Wed, 19 Feb 2020 20:40:51 +0800
Subject: [PATCH] LinkButton: use React.Fragment instead

---
 src/web/util/linkButton.coffee | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/src/web/util/linkButton.coffee b/src/web/util/linkButton.coffee
index c4a98b1..97b5ce9 100644
--- a/src/web/util/linkButton.coffee
+++ b/src/web/util/linkButton.coffee
@@ -12,17 +12,12 @@ class LinkButton extends React.Component
     # We cannot just replace the button with a <Redirect/> when we switch
     # because it will cause visual breaks where the button disappears for
     # a short while before the actual switch happens.
-    # Use <ins> as a dumb wrapper because it does not actually create
-    # an element around our tags.
-    # (the semantics of <ins> is "inserted content", but this seems
-    #  to be the only sane solution here)
-    # <https://stackoverflow.com/questions/14162035/how-to-wrap-arbitrary-html-with-a-wrapper-without-breaking-markup>
-    <ins>
+    <React.Fragment>
       <button {...@props} onClick={(e) => @setState { switch: true }}/>
       {
         @state.switch and
           <Redirect {...@props} />
       }
-    </ins>
+    </React.Fragment>
 
 export default LinkButton
\ No newline at end of file