From a224fdee7d69853d3b01fd2c8aa7c948ea3c6325 Mon Sep 17 00:00:00 2001 From: FilmKnurd Date: Thu, 12 Dec 2013 20:27:28 -0600 Subject: [PATCH] Allows you to configure which element to append the reveal - Checks for the existance of rootElement in the settings object - Uses rootElement if it is set, otherwise it appends the reveal to **Depends on PR:** #3743 Usage ---------- To change the element, pass in an a settings object on initialization: ```JS $(document).foundation( 'reveal', { rootElement: '#alternate-element'}) ``` Or on open: ```JS $('#myModal').foundation( 'reveal', 'open', { rootElement: '#alternate-element' }); ``` Purpose ------------ In a QUnit test environment, I needed the reveal to stay within the confines of the testing sandbox, so that the app code under test retained access to the modal. This feature is transparent, if no rootElement is specified, then reveal behaves exactly as expected. But, if you need to attach the reveal to another element, then you can. --- js/foundation/foundation.reveal.js | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/js/foundation/foundation.reveal.js b/js/foundation/foundation.reveal.js index 4f61b8967..f16462328 100644 --- a/js/foundation/foundation.reveal.js +++ b/js/foundation/foundation.reveal.js @@ -219,13 +219,14 @@ if (css) { var settings = el.data('reveal-init'); if (el.parent('body').length === 0) { - var placeholder = el.wrap('