Skip to content

Conversation

ajiho
Copy link

@ajiho ajiho commented Aug 6, 2025

fix #1281

I changed my mind, actually there's no need to create a new entry, just add multiple possible return scenarios

ref: val.xml#L5

Signed-off-by: ajiho <lujiahao@88.com>
Copy link

linux-foundation-easycla bot commented Aug 6, 2025

CLA Signed


The committers listed above are authorized under a signed CLA.

Copy link
Member

@mgol mgol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. I wonder if that's not going to be too confusing, maybe separating these signatures would be clearer.

If we had another similar API to compare, that'd help with alignment. .val() also has multiple return types but for a getter with no parameters so it makes sense. I'm worried here people may erroneously interpret this change as .css( propertyName ) possibly returning an array as well.

@mgol
Copy link
Member

mgol commented Aug 12, 2025

When separating, the second example would have to be moved to the signature .css( propertyNames ) as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

The documentation of CSS methods should be further classified
2 participants