This adds a test for issue #386.
…ng for now)
Previously some of core functionality referenced them via local variables, meaning overriding them on the `$.zepto` object wouldn't have effect. This removes such local variables.
…es that do not or not properly support generating touch events
…ic swipe directions
--- When theres a tap, the swipe event is fired on Nokia Symbian and Playbook tablet devices (this should not be the case since this is just a tap and not a swipe). It seems that there is a slight move when tap event is fired on these devices, so touch.x2 and touch.y2 get set. But because the delta comparison Math.abs(touch.x1 - touch.x2) > 30) and Math.abs(touch.y1 - touch.y2) > 30) are inside the conditional block that checks if touch.x2 or touch.y2 > 0, the last conditional "else if (last in touch)" is never reached. Moving the delta comparison in the conditional check fixes this issue. This has been tested on Playbook, Nokia Symbian, iPad and iPhone devices. Conflicts: src/touch.js
--- If you want to instantaneously alter the CSS of an element while some of its properties are being animated with a call to zeptos `animate()` function, the alteration to the CSS is animated too. This is because the transition was set using the shorthand syntax where only one property can be applied and all was used, eg.: `transition: all 0.3s ease-in-out;`. I have factored out the transition into the more explicit components, `transition-property`, `transition-duration` and `transition-timing-function` so that only the properties that are modified in the call to `animate()` are transitioned. This fixes my use case where an element that had an animation sprite as its background (so no transition required on `background-position`), was animated across the screen (transition required on `transform`). I have updated the test `fx.html` to reflect this change.
When DOM elements are generated via `$()`, they are now immediately orphaned (previously they belonged to a temporary internal element). When trying to insert DOM nodes around an orphan via `before()` or `after()`, they now become orphaned too (instead of the operation being a no-op). Fixes #417