From 9431e9a6e3eabf8bce4162e3aff93a8b0bdebabe Mon Sep 17 00:00:00 2001
From: Stephen Niedzielski <stephen@niedzielski.com>
Date: Wed, 28 Feb 2018 13:52:29 -0600
Subject: [PATCH] Hygiene: move CategoryAddOverlay window use to client

MinervaNeue should be solely responsible for controlling the flow of its
own UI. This patch puts the responsibility for changing the add category
dialog state when a category has successfully been added onto
MinervaNeue.

Bug: T173539
Related: Ic61ac46e21f510e5b168d7d98b68a59429eb7044
Change-Id: I5010d5ad1a27f09c1c5b0b4188dcec445cc3229f
---
 resources/skins.minerva.categories/init.js | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/resources/skins.minerva.categories/init.js b/resources/skins.minerva.categories/init.js
index f82751a..4ec2491 100644
--- a/resources/skins.minerva.categories/init.js
+++ b/resources/skins.minerva.categories/init.js
@@ -10,6 +10,9 @@
 
 		loader.loadModule( 'mobile.categories.overlays', true ).done( function ( loadingOverlay ) {
 			var CategoryOverlay = M.require( 'mobile.categories.overlays/CategoryOverlay' );
+			M.on( 'category-added', function () {
+				window.location.hash = '#/categories';
+			} );
 
 			loadingOverlay.hide();
 			result.resolve( new CategoryOverlay( {