diff --git a/dev/js/src/containermenu.js b/dev/js/src/containermenu.js
index 83e3dc6..5d3f5f3 100644
--- a/dev/js/src/containermenu.js
+++ b/dev/js/src/containermenu.js
@@ -130,9 +130,9 @@
           t.container().enter(e);
           //NEW: reset some things. These are reset for hint menu style items
           // so I believe we need to do the same when pressing on items in the container
-          t.reset("");
-          t.hide();
-          t.hint().unshow();
+          //t.reset("");
+          //t.hide();
+          //t.hint().unshow(); Moved this line into hint/menu.js because it is hint containermenu specific!
           //for clicking this is done in container.js with an eventListener for click.
         } else { // Click on item
           t.liveItem(t.position).onclick(e);
diff --git a/dev/js/src/hint/menu.js b/dev/js/src/hint/menu.js
index ecd0b51..ebbdd68 100644
--- a/dev/js/src/hint/menu.js
+++ b/dev/js/src/hint/menu.js
@@ -51,7 +51,7 @@
       obj.container().element().addEventListener("click", function (e) {
         this.reset("");
         this.element().blur();
-        this.hint().unshow(); //hide the containermenu, not with hide but with blur, because blur would usually happen in default mousedown behaviour
+        //NOW IN RESET: this.hint().unshow(); //hide the containermenu, not with hide but with blur, because blur would usually happen in default mousedown behaviour
         e.halt(); // Question: my impression is that this click event handler is called after all the others and thus this should be absolutely no problem.
         // Are we sure there are no things that do not happen now thanks to this?
 
@@ -87,6 +87,7 @@
      reset : function (action) {
       this.prefix("");
       this.hint().inputField().insert(action).update();
+      this.hint().unshow()
     },
   };
 });