luci-base: fix order of clone bug

If a rule was manipulated via cli, the rule was appended to the end if
cloned.
Somehow the reason appears to be that `name` was incorrectly assigned,
because name was the event Object this way.

Signed-off-by: Christian Korber <redacted>

diff --git a/modules/luci-base/htdocs/luci-static/resources/form.js b/modules/luci-base/htdocs/luci-static/resources/form.js
index 3d87b3d7861b01a82656739f637e4d21c81bc904..54fca6930d21edd95ecf4f6c8cb7f859cdb2e479 100644 (file)
--- a/modules/luci-base/htdocs/luci-static/resources/form.js
+++ b/modules/luci-base/htdocs/luci-static/resources/form.js
@@ -2761,7 +2761,7 @@ const CBITableSection = CBITypedSection.extend(/** @lends LuCI.form.TableSection
         * @param {string} name
         * @returns {null}
         */
-       handleClone(section_id, put_next, name) {
+       handleClone(section_id, put_next, ev, name) {
                let config_name = this.uciconfig || this.map.config;
 
                this.map.data.clone(config_name, this.sectiontype, section_id, put_next, name);