зеркало из https://github.com/mozilla/gecko-dev.git
ad65eafe7c
Currently, this bug does not occur actually because nobody has not accessed these command classes directly and they are registered only in command table for HTML editor. However, once rewriting `nsHTMLDocument::ExecCommand()` with these classes, its `IsCommandEnabled()` should return false if given editor is `TextEditor`. The reason why we need this fix is, when we make `ExecCommand()` call `IsCommandEnabled()` and it returns `true`, `ExecCommand()` needs to call `DoCommand()`. Then, it throws exception if given editor is not an `HTMLEditor` but the command class is only for `HTMLEditor`. This patch adds new WPT for testing whether `document.execCommand()` works with `<input>` and `<textarea>`. The behavior has not been standardized, but Chromium handles some commands even in it. So, I write the expectations from the point of view of web developers. (Chrome fails in "cut", "copy" and "removeformat" cases.) Differential Revision: https://phabricator.services.mozilla.com/D29473 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| awsy | ||
| config | ||
| crashtest | ||
| extensions | ||
| firefox-ui | ||
| geckodriver | ||
| gtest | ||
| jsshell | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| profiles | ||
| raptor | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| tools | ||
| tps | ||
| web-platform | ||
| webdriver | ||
| xpcshell | ||
| README.txt | ||
| addtest.py | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| moz.build | ||
| parse_build_tests_ccov.py | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| testsuite-targets.mk | ||
README.txt
Common testing tools for mozilla codebase projects, test suite definitions for automated test runs, tests that don't fit anywhere else, and other fun stuff