Bugzilla

(In reply to Emilio Cobos Álvarez (:emilio) from comment #83)
> Quite surprising, that alert, but... yay?

My patches omit redundant `Selection` updates while the editor touches the DOM tree multiple times at handling one edit. Therefore, they may improve the performance of benchmarks if they use editing API.

Note that, in strictly speaking, my patches change the behavior from point of view of legacy DOM mutation event listeners. They could cause breaking existing apps, but such apps should be rare because the other browsers put the events into the queue (like `nsContentUtils::AddScriptRunner` and dispatches them after finishing to touch the DOM tree), so, the changes should work with actual web apps in the wild.

(In reply to Emilio Cobos Álvarez (:emilio) from comment #83)
> Quite surprising, that alert, but... yay?

My patches omit redundant `Selection` updates while the editor touches the DOM tree multiple times at handling one edit. Therefore, they may improve the performance of benchmarks if they use editing API.

Note that, in strictly speaking, my patches change the behavior from point of view of legacy DOM mutation event listeners. They could cause breaking existing apps, but such apps should be rare because the other browsers put the events into the queue (like `nsContentUtils::AddScriptRunner`) and dispatches them after finishing to touch the DOM tree, so, the changes should work with actual web apps in the wild.