forked from mirrors/gecko-dev
These loops may run script. In `HyperTextAccessible`, it calls `RemoveRangeAndUnselectFramesAndNotifyListeners`. So, chrome script which is not directly related to this module may run in each call. I think that using `RemoveAllRanges` is better for here. Before bug 1735446, this loop tried to keep first range, but accidentally, I changed this loop delete all ranges. However, `SetSelectionBoundsAt` will add a range if it's required and there is no bug reports. Therefore, I think keep the new behavior is better. In `nsRange::DeleteFromDocument`, the loop may run mutation events too. Therefore, it needs to store all ranges first. Then, the preceding patch changes the behavior here if a selection range is moved to different root. Previously, it was deleted, but now, they are not touched. Depends on D200606 Differential Revision: https://phabricator.services.mozilla.com/D200607 |
||
|---|---|---|
| .. | ||
| android | ||
| aom | ||
| atk | ||
| base | ||
| basetypes | ||
| docs | ||
| generic | ||
| html | ||
| interfaces | ||
| ipc | ||
| mac | ||
| other | ||
| tests | ||
| windows | ||
| xpcom | ||
| xul | ||
| moz.build | ||