I guess when talking about one method in this realm, it would mean that people would also expect lastElementChild, childElementCount, nextElementSibling, previousElementSibling to be available. And maybe even getElementsBy... methods.

It will not be the highest priority by the maintainers, but it will also not be rejected.

It's related to the discussion regarding supporting more things from the living standard #176 and also regarding providing the correct actual types #285 instead of relying on the ones from typescript.

Yes, ideally it should implement the other Element class APIs, too.

Hey @karfau,
I would be very interested to work on this. The issue is quite old, is it something that is still "not rejected" by the maintainers?

@KevinYeramian anything that is aligned with the spec and is not requiring major rewrites or new dependencies is always welcome.

You can always expect feedback and suggestions how to improve the contribution, but most likely no substantial code contributions by maintainers.
And we will expect unit tests for every new API including those for edge cases.
Ideally you can provide small chunks of changes/multiple focused PRs, so reviewing each is easier for us.
In this case maybe adding useful pairs of APIs.

@karfau thank you for the answer.

I just create the PR #398.