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

Updated .scale() mixin so that it accepts optional vertical scale factor... #11748

Merged
merged 1 commit into from
Dec 8, 2013
Merged

Updated .scale() mixin so that it accepts optional vertical scale factor... #11748

merged 1 commit into from
Dec 8, 2013

Conversation

bganicky
Copy link
Contributor

@bganicky bganicky commented Dec 6, 2013

... parameter.

@bganicky
Copy link
Contributor Author

bganicky commented Dec 6, 2013

Now, the .scale() mixin accepts only one parameter and therefore scales both x-axis and y-axis by the same factor. I've added optional second parameter for y-axis scale factor. This change is backward compatible because you can still use just the first param resulting in a same behavior as before the change.

mdo added a commit that referenced this pull request Dec 8, 2013
Updated .scale() mixin so that it accepts optional vertical scale factor...
@mdo mdo merged commit e43e87b into twbs:master Dec 8, 2013
@mdo mdo mentioned this pull request Dec 8, 2013
@bganicky bganicky deleted the patch-1 branch December 8, 2013 21:49
pytkin added a commit to designmodo/Flat-UI that referenced this pull request Feb 5, 2014
so that it accepts optional vertical scale as second parameter.
twbs/bootstrap#11748
stempler pushed a commit to stempler/bootstrap that referenced this pull request Apr 11, 2014
Updated .scale() mixin so that it accepts optional vertical scale factor...
stempler pushed a commit to stempler/bootstrap that referenced this pull request Nov 4, 2014
Updated .scale() mixin so that it accepts optional vertical scale factor...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants