Mark VanLandingham 64438fff25 FIX: Bind events properly in search-menu.js & fix focus issue (#25006) ... The problem: Removing the options to addEventListener results in events that are properly cleaned up when the search menu is removed. Previously every time you opened the search menu, the listeners would be attached again, and clicking outside even after it was closed would fire the function again and again (N times as you opened the search menu!) This was made far far worse in this commit c91d053, where I called close() to remove focus from the search input in the event that the search menu is rendered outside the header. The problem with this was 2-fold. The close function tried to focus the search header button in core here. When the events aren't cleanup up and that happens... you can't do anything in the app. The solution: We don't need the event listeners to close the search menu when it's rendered from the header. The widget header handles clicks outside of the header. Sooo 1. Only register them for standalone search menus 2. Remove the passive options to the listeners so that they are properly removed on close 3. Call close() to unfocus input rather than just closing panel 4. Rename passed in are closeSearchMenu -> onClose because it's more accurate. It's really a callback.		2023-12-22 09:48:00 -06:00
..
images	FIX: Use correct location for wizard background image (#24183)	2023-10-31 15:57:47 +00:00
javascripts	FIX: Bind events properly in search-menu.js & fix focus issue (#25006)	2023-12-22 09:48:00 -06:00
stylesheets	UX: File types site setting (#24976)	2023-12-22 11:23:42 +11:00