Closed
Bug 1697078
Opened 4 years ago
Closed 4 years ago
Make `Document::ExecCommand` not throw exception when editor returns error
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
88 Branch
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(1 file)
Chrome does not throw exception when the Document
object handles the command with editor.
https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/editing/commands/document_exec_command.cc;l=62-100;drc=4995be9c30c3bde2bb32ab826db2d2dccf945cf3
Assignee | ||
Comment 1•4 years ago
|
||
According to the source code of Chromium, we should throw exceptions from
them only when the document is not for HTML nor XHTML. For the other reasons,
we should not throw any exceptions even if it's unknown command.
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/2c071449e0ed
Make `Document#execCommand` and related methods never throw exceptions r=smaug
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/28110 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
Comment 5•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox88:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•