зеркало из https://github.com/mozilla/gecko-dev.git
77e7a5575a
Really, there are only two cases we need to worry about. Either IsSelectionCached(), and then our SelectionProperties has the data we want, or not and then we have a non-null mSelCon which has the data we want. Since we are now using cached selection state a lot more (instead of initializing the editor whenever someone asks for selection state), we need to actually update it more correctly when .value is set. And since we now update the cached selection state for the case when .value has been set (to point to the end of the text), we need to change HTMLInputElement::HasCachedSelection to return false for that case. Otherwise we will always do eager editor init on value set. We handle that by not doing eager init if the cached selection is collapsed. The web platform test changes test the "update on .value set" behavior. They fail without this patch, pass with it. MozReview-Commit-ID: DDU8U4MGb23 |
||
|---|---|---|
| .. | ||
| config | ||
| crashtest | ||
| firefox-ui | ||
| gtest | ||
| instrumentation | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| profiles | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| tools | ||
| tps | ||
| web-platform | ||
| xpcshell | ||
| README.txt | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| moz.build | ||
| 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