Mozes Stumpf

[Bug]: expect().toEqual does not compare unique node properties

1

### Version 29.5.0 ### Steps to reproduce ``` it("tests the node's properties", () => { const text1 = document.createTextNode("text"); text1.customProperty = "customProperty"; const text2 = document.createTextNode("text"); expect(text1).toEqual(text2); // Passed });...

Range.compareBoundaryPoints should throw error

4

### Describe the bug `Range.compareBoundaryPoints` should throw error if the compared ranges' boundary-point's are in different tree. Documentation: [Range.compareBoundaryPoints](https://dom.spec.whatwg.org/#dom-range-compareboundarypoints) 2nd point: > If [this](https://webidl.spec.whatwg.org/#this)’s [root](https://dom.spec.whatwg.org/#concept-range-root) is not the same as...

TypeError on the Debugger after assigning a `Set` in a constructor

1

### Describe the bug Vitest extension in vscode shows TypeError after assigning a `Set` to a private property in a constructor.  ### Reproduction 1. Open the `Debugger.test.ts` file. 2....

**Describe the bug** When changing the `HTMLElement.contentEditable` property, the element does not get the `contenteditable` attribute. **To Reproduce** Repository to reproduce: https://github.com/mozesstumpf/contentEditable-attribute-should-change ``` test("ContentEditable attribute should change", () => {...

**Describe the bug** `Range.compareBoundaryPoints` should throw error instead of returning -1. **To Reproduce** Repo to reproduce: [compare-boundary-points-error](https://github.com/mozesstumpf/vitest-compareBoundaryPoints-error) ``` const text1 = document.createElement("text"); const text2 = document.createElement("text"); const range = new...

Type is not referred correctly in the while loop

5

### 🔎 Search Terms incorrect type while loop ### 🕗 Version & Regression Information Worked correctly in version 4.2.3. It doesn't work since 4.3.5. ### ⏯ Playground Link https://www.typescriptlang.org/play/?ts=5.5.4#code/MYGwhgzhAEDCAWBLEATaBTAHgF3QOxRgAkAVAWQBkBREdAW322gG8AoASAHN0mAHMAE6MAFAEoWHdsAD2eCE2bR+QvNhr1G0AL7QAvNGxIIAblaTEAM2jCAhMOWN1DVdERzsYPMHTSrABUFGUXE2djChbABXATxoPEiQEFMwrTNwnmjYh1UnRmTU1NZQSBgAlSYsXAJicmpaZwUObj5A1TEJMJl3FiVWtXrNHX1DRBM09ktrO2z+jRc3eU9vX2gAcQFPFDKgkMl2CMy4hKTJQvSomN7y3NV81kLiqDWNgm2XSvxCaFJKG8auHhXES7TqyeQ9GZ-bR6AxGUzmKy2ex9KELDxeHxWdboMDYdabN7YYIdc6HeKJZLsM77DKXSEDW4cApmR4wbG4-GvPoYHCfGq-Bn-ZpAtogmkXWLkk5U+4syLyaR0P4QAB0KHQFjc6GEACJgABaYBIVA6gA0cGNKFEpmA8uwiuVao1Wt1BpmZughOtRTtDsFqvVmrw2r1+s4LxQ+vd5s5Wz63ttCqV-qdQZDBvDOOwYYjUb6HvZeIjXvh2AAnrx0J6Uf6YYXY4ToAAfZ4E7ktwnwrrgo3IND6YMAdwtfbE8NoTFtAnKhIAXNXrrWW1KYb3UCqZvDB8aq8IpzP4x1u9JaCqQNJOHvogfytboAB6e-QCDwaQJNAAIyr9eL7dbXPKZsF0YNJ90YRt9DA1RCQ3PpTFSIA ###...

**Describe the bug** `Node.getRootNode({ composed: false })` retunrs the `Node` itself instead of the `ShadowRoot` if we do not add the `ShadowRoot` into the `document`. **To Reproduce** ```ts import {...