Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

editing/other/exec-command-without-editable-element.tentative.html has different results in Chrome browser and on wpt.fyi #49943

Open
nt1m opened this issue Jan 7, 2025 · 1 comment
Open

editing/other/exec-command-without-editable-element.tentative.html has different results in Chrome browser and on wpt.fyi #49943

nt1m opened this issue Jan 7, 2025 · 1 comment

Comments

@nt1m
Copy link
Member

nt1m commented Jan 7, 2025

These subtests have execCommand both failing with execCommand returning true in Chrome when ran in the browser, but pass with execCommand returning false in wpt.fyi:

ChildDocument.execCommand(copy, false, null) with ab[]c:
ParentDocument.execCommand(copy, false, null) with ab[]c:

This was found by @rniwa
@nt1m
Copy link
Member Author

nt1m commented Jan 7, 2025

To clarify, this is about: "ChildDocument.execCommand(copy, false, null) with ab[]c: calling execCommand" and "ParentDocument.execCommand(copy, false, null) with ab[]c: calling execCommand"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nt1m