[BUG] Playwright can't recognize [contenteditable] element inside a <button>

[Dinh246]

System info

• Playwright Version: [v1.34.3]
• Operating System: Window 11
• Browser: All
• Other info:

I've met this error when fill to contenteditable element inside a button:

We even test with this site and codegen:
https://play.vuejs.org/#eNq1kLFuwzAMRH/lqsXtUAtdCyVAt3YP0EWLEjO2AVkiZDpoYPjfS8dp/yAABx3vkSdwNh/M9WUi827ceCo9C0aSifc+9QPnIphR6IwF55IHVIpWPvl0ymkUDGOL3eo/V58UY8Z3LrF5ql58cnZbp4tUCA0cg5AqwHVv+3m+DS+Ls6pu3T7xJLi8DrmhuPNGfW8261hg769JJCfIlUmRTd0pdRn6LyGtppdwjCsjZSIlDl0/QiuAQwltCdzV+JK19QfXOJQrJOPUhdQSZB0R+pHa2fUgGmC3xE08Ns3Z/6OZ5ReROJF6
Steps

• Record edit contenteditable element inside a button.
• Record edit normal contenteditable element

Expected

Should record both fill actions in spec file

Actual

Only record the fill action with the last contenteditable element

DOM:

Source code

const inputField = this.frameLocator.locator("[contenteditable]");
    await block
      .getByRole("button")
      .or(this.page.locator("[class*=accordion__item]"))
      .nth(tab - 1)
      .dblclick();
    await inputField.waitFor();
    await this.page.keyboard.press("Control+A");
    if (typeof title !== undefined) {
      await inputField.fill(title);
    }
    await this.titleBar.click();
    await this.quickSettingsText.waitFor({ state: "hidden" });
    }

[aslushnikov]

@Dinh246 Thank you, I can repro with the following snippet:

import { chromium } from '@playwright/test';

const browser = await chromium.launch();

const page = await browser.newPage();
await page.setContent(`
  <button>
    <div contenteditable="true">foo</div>
  </button>
`);
await page.fill('[contenteditable]', 'bar');
await browser.close();

[pavelfeldman]

Why was this issue closed?

Thank you for your contribution to our project. This issue has been closed due to its limited upvotes and recent activity, and insufficient feedback for us to effectively act upon. Our priority is to focus on bugs that reflect higher user engagement and have actionable feedback, to ensure our bug database stays manageable.

Should you feel this closure was in error, please create a new issue and reference this one. We're open to revisiting it given increased support or additional clarity. Your understanding and cooperation are greatly appreciated.