We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Trying to migrate to happy-dom and our test presumes that if the anchorNode is null, then the anchorOffset is 0 To Reproduce
Steps to reproduce the behavior: https://w3c.github.io/selection-api/#dom-selection-anchoroffset
Expected behavior It matches spec
Screenshots If applicable, add screenshots to help explain your problem.
Device:
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
capricorn86#1163@patch: Selection anchorOffset should return a number.
0435acb
Merge pull request #1164 from seanogdev/fix-selection-spec
5faca75
#1163@patch: Selection anchorOffset should return a number.
Thank you again for your contribution @seanogdev!
Your fix has been released: https://github.com/capricorn86/happy-dom/releases/tag/v13.1.2
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Trying to migrate to happy-dom and our test presumes that if the anchorNode is null, then the anchorOffset is 0
To Reproduce
Steps to reproduce the behavior:
https://w3c.github.io/selection-api/#dom-selection-anchoroffset
Expected behavior
It matches spec
Screenshots
If applicable, add screenshots to help explain your problem.
Device:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: