>>> I ran into a number of times where I needed to grab a
>>> series of css values and set them all onto another,
>> This functionality overlaps with what you were proposing in #4295
> That bug has nothing to do with the caller interpreting complex
> shorthands.
I agree; I was looking at the functionality you wanted in your
original statement--grabbing a series of css values.
> I see no reason to require people to use
> $(node).css(['marginTop', 'marginRight', 'marginBottom', 'marginLeft']);
> when it's perfectly valid (and more likely) for them to try using
> $(node).css('margin');
With .css("margin") (or "border" or "padding") it seems like there is
only one thing a caller could reasonably do without parsing it--pass
it back to .css("margin", value) to be set. Are there a lot of
situations where that is needed?
I can see useful cases for .css(["prop1", "prop2"]) but not many for
css("shorthandProperty"). If you have the former, the amount of code
you need to write inside your own app will probably be less than if
you had the latter and tried to parse out the individual properties.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
