From f3f24fe7d1cabeb23be2b3b8c87be61f338c91de Mon Sep 17 00:00:00 2001
From: Dinis Correia <diniscorreia@mac.com>
Date: Wed, 16 Nov 2016 13:58:10 +0000
Subject: [PATCH] Fix dropdown destroy method
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

This fixes issue #9339. When destroying a dropdown menu, the dropdown
classes wouldn’t be removed if using a different class structure (for
instance, using custom class names instead of `.menu`). Previous
versions selected all child elements of the menu but on the latest
version only direct `li` childs or  elements with `.menu` class

This commit ensures `ul` elements also get the classes removed, for
those cases where custom classes are used.
---
 js/foundation.util.nest.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/js/foundation.util.nest.js b/js/foundation.util.nest.js
index 82603a790..67031555d 100644
--- a/js/foundation.util.nest.js
+++ b/js/foundation.util.nest.js
@@ -63,7 +63,7 @@ const Nest = {
         hasSubClass = `is-${type}-submenu-parent`;
 
     menu
-      .find('>li, .menu, .menu > li')
+      .find('>li, > li > ul, .menu, .menu > li')
       .removeClass(`${subMenuClass} ${subItemClass} ${hasSubClass} is-submenu-item submenu is-active`)
       .removeAttr('data-submenu').css('display', '');
 
-- 
2.47.2