change .getClosest to include the node itself

[ianstormtaylor]

Do you want to request a feature or report a bug?

Bug.

What's the current behavior?

Right now the .getClosest method doesn't return the node itself if it matches the iterator. This is confusing because it's different than the behavior of the DOM's native el.closest API.

What's the expected behavior?

It should return the node itself if it matches too.

[Dundercover]

Are you saying that these methods also need to change?

• getClosestBlock
• getClosestInline
• getClosestVoid

[ianstormtaylor]

@Dundercover yup, they'd need to do the same for consistency. We can always add a getClosestAncestor* if people find it a big enough use case, but I'd like the base API to match the browser's semantics.

[ianstormtaylor]

Fixed by #3093.