From: Andreas Wahlqvist Date: Tue, 1 Mar 2016 13:09:48 +0000 (+0100) Subject: fix typo javascript-utilities.md X-Git-Tag: v6.2.2-rc1~4^2~22^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F8296%2Fhead;p=thirdparty%2Ffoundation%2Ffoundation-sites.git fix typo javascript-utilities.md "strong" -> "string" --- diff --git a/docs/pages/javascript-utilities.md b/docs/pages/javascript-utilities.md index 62f979a2e..c9e21919a 100644 --- a/docs/pages/javascript-utilities.md +++ b/docs/pages/javascript-utilities.md @@ -174,4 +174,4 @@ Foundation includes a couple useful features in the core library that are used i `Foundation.getFnName(fn)` returns a string representation of a named function. Seems small, but believe us, it's useful. -`Foundation.transitionend()` is a function that returns the strong of the properly vendor-prefixed version of `transitionend` events. Most browsers don't require a prefix these days, but for those that do, we've got you covered. But IE 9 doesn't support transitions?? Quite right you are! In that case our plugins that use transitions will simply snap to whatever location or visibility state they were headed to, and this function will fire a `transitionend` event manually on the element you passed. It still gives the desired results, and allows Motion-UI to work in IE 9. +`Foundation.transitionend()` is a function that returns the string of the properly vendor-prefixed version of `transitionend` events. Most browsers don't require a prefix these days, but for those that do, we've got you covered. But IE 9 doesn't support transitions?? Quite right you are! In that case our plugins that use transitions will simply snap to whatever location or visibility state they were headed to, and this function will fire a `transitionend` event manually on the element you passed. It still gives the desired results, and allows Motion-UI to work in IE 9.