Thanks! Fixed


On Wed, Apr 10, 2013 at 12:55 PM, Roman Bataev <notifications@github.com>wrote:

> In README.md:
>
> > +## Backbone.history.stepOut
> > +
> > +Dealing with iframes within a backbone app is problematic as they push on to your history stack and
> > +under most browsers this is not easily removed from the history by removing the iframe.
> > +`Backbone.history.stepOut(options)` provides a utility to work around this shortcoming by stepping
> > +backward until the iframe's history entries are removed in addition to the current backbone route
> > +entry.
> > +
> > +Accepts an `options` hash with the following fields:
> > +
> > +* `view`: View element hosting the iframe.
> > +    Any iframes hosted in this view will be removed. It is highly recommended that this is
> > +    passed as it will reduce the chance of side effects from the iframe navigation and
> > +    under [some browsers](https://bugzilla.mozilla.org/show_bug.cgi?id=293417) it will make the
> > +    operation significantly faster.
> > +* `complete(fragment, existingTriggered)`: Callback that is called when the operation is complete
>
> Looks like it's actually callback in the code
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/walmartlabs/backbone-historytracker/pull/1/files#r3738864>
> .
>