Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adjust the parameters of the flippant.flip function for better control o... #20

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

armish
Copy link

@armish armish commented Jan 8, 2014

...ver the back element.

Changed the parameter content to the HTML element--that is the back of the card/modal--with the name back.

The older way was flawed in the sense that, when the back element was created, it was being appended to the body hence reducing the control over the flippand.

To better understand this, imagine a scenario where the developer wants to destroy the flipped card (i.e. the back element) when the user requests a new view (the Backbone-way). With the older way, it was incredibly hard to destroy the back element.

If the developer specifies the back element by himself (as this commit allows), s/he can destroy the container of the card/modals and will simply get rid of the overflowing back element whenever a new view is created.

Just a suggestion ;)

…l over the back element.

Changed the parameter `content` to the HTML element--that is the back of the card/modal--with the name `back`.

The older way was flawed in the sense that, when the `back` element was created, it was being appended to the `body` hence reducing the control over the flippand.

To better understand this, imagine a scenario where the developer wants to destroy the flipped card (i.e. the `back` element) when the user requests a new view (the Backbone-way). With the older way, it was incredibly hard to destroy the back element.

If the developer specifies the `back` element by himself (as this commit allows), s/he can destroy the container of the card/modals and will simply get rid of the overflowing back element whenever a new view is created.

Just a suggestion ;)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant