From a3c63daf106482c6214307b27cbe55a1bacab5e3 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Julian=20=C4=86wirko?= Date: Wed, 16 Dec 2015 13:18:17 +0100 Subject: [PATCH] Update meteor-README.md - Fixed internal hash anchors. It isn't working on Atmospherejs.com. - Added 'Known problems' section with explanation of one problem with events which is a corner case and is explained in the issue #7248 (last comments) --- meteor-README.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/meteor-README.md b/meteor-README.md index 76f140390..e164541d9 100644 --- a/meteor-README.md +++ b/meteor-README.md @@ -4,8 +4,8 @@ Foundation is the most advanced responsive front-end framework in the world. Qui ## Usage in Meteor -- [Scss guide](#scss-guide) -- [JavaScript guide](#javascript-guide) +- [Scss guide](meteor-README.md/#scss-guide) +- [JavaScript guide](meteor-README.md/#javascript-guide) ## Scss Guide @@ -142,3 +142,9 @@ Template.myReveal.onDestroyed(function () { As you can see it is better to create small templates for plugins and initiate the plugins separately in the `onRendered` lifecycle hook. You should also remember to destroy the plugin using `onDestroyed`lifecycle hook on its template. You will find more info about particular plugins on its docs page here: [http://foundation.zurb.com/sites/docs/](http://foundation.zurb.com/sites/docs/) + +#### Known problems + +1. **Conflicts with Meteor events**. +Solution: Try to always wrap Foundation's DOM nodes into another ones in your Meteor templates. This applies only to nodes on which are initialized Foundation's JS plugins and which are the first nodes in the Meteor templates with attached custom Meteor events. For more details read the last comments here: [#7248](https://github.com/zurb/foundation-sites/issues/7248) + -- 2.47.2