1) [chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('add missing href at hydration') Expected string: "/some-url" Received string: "" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('add missing href at hydration') - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" 21 | test( 'add missing href at hydration', async ( { page } ) => { 22 | const el = page.getByTestId( 'add missing href at hydration' ); > 23 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 24 | } ); 25 | 26 | test( 'change href at hydration', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:23:22

1) [chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('add missing href at hydration') Expected string: "/some-url" Received string: "" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('add missing href at hydration') - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" 21 | test( 'add missing href at hydration', async ( { page } ) => { 22 | const el = page.getByTestId( 'add missing href at hydration' ); > 23 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 24 | } ); 25 | 26 | test( 'change href at hydration', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:23:22

1) [chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('add missing href at hydration') Expected string: "/some-url" Received string: "" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('add missing href at hydration') - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" 21 | test( 'add missing href at hydration', async ( { page } ) => { 22 | const el = page.getByTestId( 'add missing href at hydration' ); > 23 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 24 | } ); 25 | 26 | test( 'change href at hydration', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:23:22

2) [chromium] › interactivity/directive-bind.spec.ts:26:6 › data-wp-bind › change href at hydration Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('change href at hydration') Expected string: "/some-url" Received string: "/other-url" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('change href at hydration') - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" 26 | test( 'change href at hydration', async ( { page } ) => { 27 | const el = page.getByTestId( 'change href at hydration' ); > 28 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 29 | } ); 30 | 31 | test( 'update missing href at hydration', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:28:22

2) [chromium] › interactivity/directive-bind.spec.ts:26:6 › data-wp-bind › change href at hydration Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('change href at hydration') Expected string: "/some-url" Received string: "/other-url" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('change href at hydration') - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" 26 | test( 'change href at hydration', async ( { page } ) => { 27 | const el = page.getByTestId( 'change href at hydration' ); > 28 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 29 | } ); 30 | 31 | test( 'update missing href at hydration', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:28:22

2) [chromium] › interactivity/directive-bind.spec.ts:26:6 › data-wp-bind › change href at hydration Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('change href at hydration') Expected string: "/some-url" Received string: "/other-url" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('change href at hydration') - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" - locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a> - unexpected value "/other-url" 26 | test( 'change href at hydration', async ( { page } ) => { 27 | const el = page.getByTestId( 'change href at hydration' ); > 28 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 29 | } ); 30 | 31 | test( 'update missing href at hydration', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:28:22

3) [chromium] › interactivity/directive-bind.spec.ts:31:6 › data-wp-bind › update missing href at hydration Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('add missing href at hydration') Expected string: "/some-url" Received string: "" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('add missing href at hydration') - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" 31 | test( 'update missing href at hydration', async ( { page } ) => { 32 | const el = page.getByTestId( 'add missing href at hydration' ); > 33 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 34 | await page.getByTestId( 'toggle' ).click(); 35 | await expect( el ).toHaveAttribute( 'href', '/some-other-url' ); 36 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:33:22

3) [chromium] › interactivity/directive-bind.spec.ts:31:6 › data-wp-bind › update missing href at hydration Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('add missing href at hydration') Expected string: "/some-url" Received string: "" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('add missing href at hydration') - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" 31 | test( 'update missing href at hydration', async ( { page } ) => { 32 | const el = page.getByTestId( 'add missing href at hydration' ); > 33 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 34 | await page.getByTestId( 'toggle' ).click(); 35 | await expect( el ).toHaveAttribute( 'href', '/some-other-url' ); 36 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:33:22

3) [chromium] › interactivity/directive-bind.spec.ts:31:6 › data-wp-bind › update missing href at hydration Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('add missing href at hydration') Expected string: "/some-url" Received string: "" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('add missing href at hydration') - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" - locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a> - unexpected value "null" 31 | test( 'update missing href at hydration', async ( { page } ) => { 32 | const el = page.getByTestId( 'add missing href at hydration' ); > 33 | await expect( el ).toHaveAttribute( 'href', '/some-url' ); | ^ 34 | await page.getByTestId( 'toggle' ).click(); 35 | await expect( el ).toHaveAttribute( 'href', '/some-other-url' ); 36 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:33:22

4) [chromium] › interactivity/directive-bind.spec.ts:38:6 › data-wp-bind › add missing checked at hydration Error: Timed out 5000ms waiting for expect(locator).toBeChecked() Locator: getByTestId('add missing checked at hydration') Expected: checked Received: unchecked Call log: - expect.toBeChecked with timeout 5000ms - waiting for getByTestId('add missing checked at hydration') - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" - locator resolved to <input type="checkbox" data-wp-bind--checked="state.che…/> - unexpected value "unchecked" 38 | test( 'add missing checked at hydration', async ( { page } ) => { 39 | const el = page.getByTestId( 'add missing checked at hydration' ); > 40 | await expect( el ).toBeChecked(); | ^ 41 | } ); 42 | 43 | test( 'remove existing checked at hydration', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:40:22

1) [chromium] › interactivity/directive-watch.spec.ts:21:6 › data-wp-watch › check that watch runs when it is added Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: getByTestId('element in the DOM') Expected string: "element is in the DOM" Received string: "" Call log: - expect.toContainText with timeout 5000ms - waiting for getByTestId('element in the DOM') - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" 21 | test( 'check that watch runs when it is added', async ( { page } ) => { 22 | const el = page.getByTestId( 'element in the DOM' ); > 23 | await expect( el ).toContainText( 'element is in the DOM' ); | ^ 24 | } ); 25 | 26 | test( 'check that watch runs when it is removed', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:23:22

1) [chromium] › interactivity/directive-watch.spec.ts:21:6 › data-wp-watch › check that watch runs when it is added Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: getByTestId('element in the DOM') Expected string: "element is in the DOM" Received string: "" Call log: - expect.toContainText with timeout 5000ms - waiting for getByTestId('element in the DOM') - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" 21 | test( 'check that watch runs when it is added', async ( { page } ) => { 22 | const el = page.getByTestId( 'element in the DOM' ); > 23 | await expect( el ).toContainText( 'element is in the DOM' ); | ^ 24 | } ); 25 | 26 | test( 'check that watch runs when it is removed', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:23:22

1) [chromium] › interactivity/directive-watch.spec.ts:21:6 › data-wp-watch › check that watch runs when it is added Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: getByTestId('element in the DOM') Expected string: "element is in the DOM" Received string: "" Call log: - expect.toContainText with timeout 5000ms - waiting for getByTestId('element in the DOM') - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" 21 | test( 'check that watch runs when it is added', async ( { page } ) => { 22 | const el = page.getByTestId( 'element in the DOM' ); > 23 | await expect( el ).toContainText( 'element is in the DOM' ); | ^ 24 | } ); 25 | 26 | test( 'check that watch runs when it is removed', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:23:22

2) [chromium] › interactivity/directive-watch.spec.ts:26:6 › data-wp-watch › check that watch runs when it is removed Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: getByTestId('element in the DOM') Expected string: "element is not in the DOM" Received string: "" Call log: - expect.toContainText with timeout 5000ms - waiting for getByTestId('element in the DOM') - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" 27 | await page.getByTestId( 'toggle' ).click(); 28 | const el = page.getByTestId( 'element in the DOM' ); > 29 | await expect( el ).toContainText( 'element is not in the DOM' ); | ^ 30 | } ); 31 | 32 | test( 'change focus after DOM changes', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:29:22

2) [chromium] › interactivity/directive-watch.spec.ts:26:6 › data-wp-watch › check that watch runs when it is removed Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: getByTestId('element in the DOM') Expected string: "element is not in the DOM" Received string: "" Call log: - expect.toContainText with timeout 5000ms - waiting for getByTestId('element in the DOM') - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" 27 | await page.getByTestId( 'toggle' ).click(); 28 | const el = page.getByTestId( 'element in the DOM' ); > 29 | await expect( el ).toContainText( 'element is not in the DOM' ); | ^ 30 | } ); 31 | 32 | test( 'change focus after DOM changes', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:29:22

2) [chromium] › interactivity/directive-watch.spec.ts:26:6 › data-wp-watch › check that watch runs when it is removed Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: getByTestId('element in the DOM') Expected string: "element is not in the DOM" Received string: "" Call log: - expect.toContainText with timeout 5000ms - waiting for getByTestId('element in the DOM') - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" - locator resolved to <div data-testid="element in the DOM" data-wp-text="s…></div> - unexpected value "" 27 | await page.getByTestId( 'toggle' ).click(); 28 | const el = page.getByTestId( 'element in the DOM' ); > 29 | await expect( el ).toContainText( 'element is not in the DOM' ); | ^ 30 | } ); 31 | 32 | test( 'change focus after DOM changes', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:29:22

3) [chromium] › interactivity/directive-watch.spec.ts:32:6 › data-wp-watch › change focus after DOM changes Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByTestId('input') Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByTestId('input') - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" 32 | test( 'change focus after DOM changes', async ( { page } ) => { 33 | const el = page.getByTestId( 'input' ); > 34 | await expect( el ).toBeFocused(); | ^ 35 | await page.getByTestId( 'toggle' ).click(); 36 | await page.getByTestId( 'toggle' ).click(); 37 | await expect( el ).toBeFocused(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:34:22

3) [chromium] › interactivity/directive-watch.spec.ts:32:6 › data-wp-watch › change focus after DOM changes Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByTestId('input') Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByTestId('input') - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" 32 | test( 'change focus after DOM changes', async ( { page } ) => { 33 | const el = page.getByTestId( 'input' ); > 34 | await expect( el ).toBeFocused(); | ^ 35 | await page.getByTestId( 'toggle' ).click(); 36 | await page.getByTestId( 'toggle' ).click(); 37 | await expect( el ).toBeFocused(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:34:22

3) [chromium] › interactivity/directive-watch.spec.ts:32:6 › data-wp-watch › change focus after DOM changes Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByTestId('input') Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByTestId('input') - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" - locator resolved to <input data-testid="input" data-wp-watch="callbacks.ele…/> - unexpected value "not focused" 32 | test( 'change focus after DOM changes', async ( { page } ) => { 33 | const el = page.getByTestId( 'input' ); > 34 | await expect( el ).toBeFocused(); | ^ 35 | await page.getByTestId( 'toggle' ).click(); 36 | await page.getByTestId( 'toggle' ).click(); 37 | await expect( el ).toBeFocused(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:34:22

4) [chromium] › interactivity/directive-watch.spec.ts:40:6 › data-wp-watch › short-circuit infinite loops Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: getByTestId('short-circuit infinite loops') - Expected string - 1 + Received string + 3 - 1 + + 0 + Call log: - expect.toContainText with timeout 5000ms - waiting for getByTestId('short-circuit infinite loops') - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " - locator resolved to <div data-wp-text="state.counter" data-wp-watch="call…>↵⇆⇆0↵⇆</div> - unexpected value " 0 " 40 | test( 'short-circuit infinite loops', async ( { page } ) => { 41 | const el = page.getByTestId( 'short-circuit infinite loops' ); > 42 | await expect( el ).toContainText( '1' ); | ^ 43 | await page.getByTestId( 'increment' ).click(); 44 | await expect( el ).toContainText( '3' ); 45 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-watch.spec.ts:42:22

1) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:368:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Submenu Link' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Submenu Link' }) 414 | // Move the mouse so the hover on the button doesn't keep the menu open 415 | await page.mouse.move( 400, 400 ); > 416 | await expect( firstLevelElement ).toBeVisible(); | ^ 417 | await expect( secondLevelElement ).toBeHidden(); 418 | 419 | // Close menu via click on the body at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:416:38

1) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:368:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Submenu Link' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Submenu Link' }) 414 | // Move the mouse so the hover on the button doesn't keep the menu open 415 | await page.mouse.move( 400, 400 ); > 416 | await expect( firstLevelElement ).toBeVisible(); | ^ 417 | await expect( secondLevelElement ).toBeHidden(); 418 | 419 | // Close menu via click on the body at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:416:38

1) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:368:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Submenu Link' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Submenu Link' }) 414 | // Move the mouse so the hover on the button doesn't keep the menu open 415 | await page.mouse.move( 400, 400 ); > 416 | await expect( firstLevelElement ).toBeVisible(); | ^ 417 | await expect( secondLevelElement ).toBeHidden(); 418 | 419 | // Close menu via click on the body at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:416:38

2) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:458:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Subpage' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Subpage' }) 471 | // page-list submenu opens on click 472 | await submenuButton.click(); > 473 | await expect( innerElement ).toBeVisible(); | ^ 474 | 475 | // page-list submenu closes on click outside 476 | await page.click( 'body' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:473:33

2) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:458:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Subpage' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Subpage' }) 471 | // page-list submenu opens on click 472 | await submenuButton.click(); > 473 | await expect( innerElement ).toBeVisible(); | ^ 474 | 475 | // page-list submenu closes on click outside 476 | await page.click( 'body' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:473:33

2) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:458:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Subpage' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Subpage' }) 471 | // page-list submenu opens on click 472 | await submenuButton.click(); > 473 | await expect( innerElement ).toBeVisible(); | ^ 474 | 475 | // page-list submenu closes on click outside 476 | await page.click( 'body' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:473:33

Process completed with exit code 1.

1) [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:75:3

1) [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:75:3

1) [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:75:3

2) [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('a').filter({ hasText: 'Custom Link' }) Expected string: "rgb(0, 0, 0)" Received string: "rgb(255, 255, 255)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('a').filter({ hasText: 'Custom Link' }) - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. > 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); | ^ 491 | await expect( submenuLink ).toHaveCSS( 'color', submenuTextColor ); 492 | await expect( pageLink ).toHaveCSS( 'color', submenuTextColor ); 493 | at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:490:30) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:128:3

2) [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('a').filter({ hasText: 'Custom Link' }) Expected string: "rgb(0, 0, 0)" Received string: "rgb(255, 255, 255)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('a').filter({ hasText: 'Custom Link' }) - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. > 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); | ^ 491 | await expect( submenuLink ).toHaveCSS( 'color', submenuTextColor ); 492 | await expect( pageLink ).toHaveCSS( 'color', submenuTextColor ); 493 | at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:490:30) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:128:3

2) [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('a').filter({ hasText: 'Custom Link' }) Expected string: "rgb(0, 0, 0)" Received string: "rgb(255, 255, 255)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('a').filter({ hasText: 'Custom Link' }) - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. > 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); | ^ 491 | await expect( submenuLink ).toHaveCSS( 'color', submenuTextColor ); 492 | await expect( pageLink ).toHaveCSS( 'color', submenuTextColor ); 493 | at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:490:30) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:128:3

3) [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:184:3

3) [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:184:3

3) [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:184:3

4) [chromium] › editor/blocks/navigation-colors.spec.js:187:2 › Navigation colors › The navigation text color should apply to all navigation links including submenu and overlay text Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:226:3

11 skipped 151 passed (7.5m)

135 passed (6.4m)

1 skipped 150 passed (6.5m)

35 failed [chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration [chromium] › interactivity/directive-bind.spec.ts:26:6 › data-wp-bind › change href at hydration [chromium] › interactivity/directive-bind.spec.ts:31:6 › data-wp-bind › update missing href at hydration [chromium] › interactivity/directive-bind.spec.ts:38:6 › data-wp-bind › add missing checked at hydration [chromium] › interactivity/directive-bind.spec.ts:43:6 › data-wp-bind › remove existing checked at hydration [chromium] › interactivity/directive-bind.spec.ts:48:6 › data-wp-bind › update existing checked [chromium] › interactivity/directive-bind.spec.ts:70:6 › data-wp-bind › nested binds ─────────── [chromium] › interactivity/directive-bind.spec.ts:80:6 › data-wp-bind › check enumerated attributes with true/false values [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › width is correctly hydrated for different values [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › name is correctly hydrated for different values [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › disabled is correctly hydrated for different values [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › aria-disabled is correctly hydrated for different values [chromium] › interactivity/directive-init.spec.ts:21:6 › data-wp-init › should run when the block renders [chromium] › interactivity/directive-init.spec.ts:27:6 › data-wp-init › should not run again if accessed signals change [chromium] › interactivity/directive-init.spec.ts:37:6 › data-wp-init › should run multiple inits if defined [chromium] › interactivity/directive-init.spec.ts:43:6 › data-wp-init › should run the init callback when the element is unmounted [chromium] › interactivity/directive-init.spec.ts:60:6 › data-wp-init › should run init when the element is mounted [chromium] › interactivity/directive-key.spec.ts:21:6 › data-wp-key › should keep the elements when adding items to the start of the array [chromium] › interactivity/directive-on.spec.ts:21:6 › data-wp-on › callbacks should run whenever the specified event is dispatched [chromium] › interactivity/directive-on.spec.ts:31:6 › data-wp-on › callbacks should receive the dispatched event [chromium] › interactivity/directive-on.spec.ts:39:6 › data-wp-on › callbacks should be able to access the context [chromium] › interactivity/directive-on.spec.ts:47:6 › data-wp-on › should work with custom events [chromium] › interactivity/directive-priorities.spec.ts:21:6 › Directives (w/ priority) › should run in priority order [chromium] › interactivity/directive-priorities.spec.ts:28:6 › Directives (w/ priority) › should wrap those with less priority [chromium] › interactivity/directive-priorities.spec.ts:42:6 › Directives (w/ priority) › should propagate element modifications top-down [chromium] › interactivity/directive-priorities.spec.ts:85:6 › Directives (w/ priority) › should not create a Directives component if none of the directives are registered [chromium] › interactivity/directive-slots.spec.ts:21:6 › data-wp-slot › should render the fill in its children by default [chromium] › interactivity/directive-slots.spec.ts:42:6 › data-wp-slot › should render the fill before if specified [chromium] › interactivity/directive-slots.spec.ts:62:6 › data-wp-slot › should render the fill after if specified [chromium] › interactivity/directive-slots.spec.ts:82:6 › data-wp-slot › should render the fill in its children if specified [chromium] › interactivity/directive-slots.spec.ts:103:6 › data-wp-slot › should be replaced by the fill if specified [chromium] › interactiv

133 passed (6.6m)

59 failed [chromium] › interactivity/directive-watch.spec.ts:21:6 › data-wp-watch › check that watch runs when it is added [chromium] › interactivity/directive-watch.spec.ts:26:6 › data-wp-watch › check that watch runs when it is removed [chromium] › interactivity/directive-watch.spec.ts:32:6 › data-wp-watch › change focus after DOM changes [chromium] › interactivity/directive-watch.spec.ts:40:6 › data-wp-watch › short-circuit infinite loops [chromium] › interactivity/directives-body.spec.ts:21:6 › data-wp-body › should move the element to the document's body [chromium] › interactivity/directives-body.spec.ts:33:6 › data-wp-body › should make context accessible for inner elements [chromium] › interactivity/directives-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value [chromium] › interactivity/directives-class.spec.ts:34:6 › data-wp-class › add class if callback returns truthy value [chromium] › interactivity/directives-class.spec.ts:45:6 › data-wp-class › handles multiple classes and callbacks [chromium] › interactivity/directives-class.spec.ts:58:6 › data-wp-class › handles class names that are contained inside other class names [chromium] › interactivity/directives-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle [chromium] › interactivity/directives-class.spec.ts:80:6 › data-wp-class › can toggle class when class attribute is missing [chromium] › interactivity/directives-class.spec.ts:93:6 › data-wp-class › can use context values [chromium] › interactivity/directives-class.spec.ts:102:6 › data-wp-class › can use BEM notation classes [chromium] › interactivity/directives-class.spec.ts:107:6 › data-wp-class › can use classes with several dashes [chromium] › interactivity/directives-context.spec.ts:28:6 › data-wp-context › is correctly initialized [chromium] › interactivity/directives-context.spec.ts:41:6 › data-wp-context › is correctly extended [chromium] › interactivity/directives-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected (child) [chromium] › interactivity/directives-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected (parent) [chromium] › interactivity/directives-context.spec.ts:97:6 › data-wp-context › changes in shadowed properties do not leak (child) [chromium] › interactivity/directives-context.spec.ts:118:6 › data-wp-context › changes in shadowed properties do not leak (parent) [chromium] › interactivity/directives-context.spec.ts:139:6 › data-wp-context › Array properties are shadowed [chromium] › interactivity/directives-context.spec.ts:152:6 › data-wp-context › can be accessed in other directives on the same element [chromium] › interactivity/directives-context.spec.ts:166:6 › data-wp-context › should replace values on navigation [chromium] › interactivity/directives-context.spec.ts:175:6 › data-wp-context › should preserve the previous context values [chromium] › interactivity/directives-context.spec.ts:184:6 › data-wp-context › should maintain the same context reference on async actions [chromium] › interactivity/directives-style.spec.ts:33:6 › data-wp-style › remove style if callback returns falsy value on hydration [chromium] › interactivity/directives-style.spec.ts:42:6 › data-wp-style › change style if callback returns a new value on hydration [chromium] › interactivity/directives-style.spec.ts:54:6 › data-wp-style › handles multiple styles and callbacks on hydration [chromium] › interactivity/directives-style.spec.ts:66:6 › data-wp-style › can add style when style attribute is missing on hydration [chromium] › interactivity/directives-style.spec.ts:75:6 › data-wp-style › can toggle style ──── [chromium] › interactivity/directives-style.spec.ts:82:6 › data-wp-style › can remove style ──── [chromium] › interactivity/directives-style.spec.ts:89:6 › data-wp-style › can toggle style in the middle [chromium] › int

2 failed [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:368:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:458:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions 2 skipped 117 passed (9.1m)