From f3183a709fae948af62157d8ff6d40456f15ad56 Mon Sep 17 00:00:00 2001 From: Yoshiki Shibukawa Date: Mon, 13 Apr 2015 08:47:08 +0900 Subject: [PATCH] Update mithril.md Fix spelling --- docs/mithril.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/mithril.md b/docs/mithril.md index 19f7a706..bebf617a 100644 --- a/docs/mithril.md +++ b/docs/mithril.md @@ -8,7 +8,7 @@ - [Accessing the real DOM element](#accessing-the-real-dom-element) - [Persisting config data](#persisting-config-data) - [Destructors](#destructors) -- [Persising DOM elements across route changes](#persising-dom-elements-across-route-changes) +- [Persisting DOM elements across route changes](#persisting-dom-elements-across-route-changes) - [SVG](#svg) - [Dealing with focus](#dealing-with-focus) - [Dealing with sorting and deleting in lists](#dealing-with-sorting-and-deleting-in-lists) @@ -343,7 +343,7 @@ m.render(document, m("a")); //logs `unloaded the div` and `alert` never gets cal --- -#### Persising DOM elements across route changes +#### Persisting DOM elements across route changes When using the [router](mithril.route.md), a route change recreates the DOM tree from scratch in order to unload plugins from the previous page. If you want to keep a DOM element intact across a route change, you can set the `retain` flag in the config's context object.