fix: add Locator as a possible element type in toContainElement() matcher (fix #8910) (#8927)

vitalybaev · web-flow · commit 35a27d4b331f · 2025-11-04T11:55:12.000+01:00
diff --git a/docs/guide/browser/assertion-api.md b/docs/guide/browser/assertion-api.md
@@ -324,7 +324,7 @@ await expect.element(page.getByText('Vitest')).toBeInViewport({ ratio: 1 })
 ## toContainElement
 
 ```ts
-function toContainElement(element: HTMLElement | SVGElement | null): Promise<void>
+function toContainElement(element: HTMLElement | SVGElement | Locator | null): Promise<void>
 ```
 
 This allows you to assert whether an element contains another element as a descendant or not.
diff --git a/packages/browser/jest-dom.d.ts b/packages/browser/jest-dom.d.ts
@@ -1,7 +1,7 @@
 // Disable automatic exports.
 
 import { ARIARole } from './aria-role.ts'
-import { ScreenshotComparatorRegistry, ScreenshotMatcherOptions } from './context.js'
+import { Locator, ScreenshotComparatorRegistry, ScreenshotMatcherOptions } from './context.js'
 
 export interface TestingLibraryMatchers<E, R> {
   /**
@@ -207,7 +207,7 @@ export interface TestingLibraryMatchers<E, R> {
    * await expect.element(ancestor).not.toContainElement(nonExistentElement)
    * @see https://vitest.dev/guide/browser/assertion-api#tocontainelement
    */
-  toContainElement(element: HTMLElement | SVGElement | null): R
+  toContainElement(element: HTMLElement | SVGElement | Locator | null): R
   /**
    * @description
    * Assert whether a string representing a HTML element is contained in another element.
