From 58cfe6691d8d479c55e46d9bc6c938e0ade5bf75 Mon Sep 17 00:00:00 2001
From: Juuso Lapinlampi <wub@partyvan.eu>
Date: Sun, 27 Sep 2015 13:30:29 +0000
Subject: Remove misleading comment and simplify pomf.js case 413
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

There appears to be no such thing as a terrible scary bug that needs a
workaround in my Chromium 45.0.2454.85 browser to encode &hellip;. The
unobvious self-closing <div/> is also very questionable.

For what it's worth, &hellip; will encode correctly as long as you use
jQuery's .html() method – which it already did anyway.

OK ewhal@
---
 js/pomf.js | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/js/pomf.js b/js/pomf.js
index c3f52bc..2cea939 100644
--- a/js/pomf.js
+++ b/js/pomf.js
@@ -160,10 +160,7 @@ $(function() {
           break;
         case 413:
           uploadFiles.addClass('error completed');
-          // Terrible work-around, but necessary since otherwise the '&hellip;'
-          // entity is left decoded.
-          totalName.html($('<div/>').html('onii-chan, y-your upload is t-too ' +
-            'big&hellip;').text());
+          totalName.html('onii-chan, y-your upload is t-too big&hellip;');
           break;
         default:
           uploadFiles.addClass('error completed');
-- 
cgit v1.2.3