pdf.js

History

Jonas Jenwald 4ef1a129fa Replace the remaining `Node.removeChild()` instances with `Element.remove()` Using `Element.remove()` is a slightly more compact way of removing an element, since you no longer need to explicitly find/use its parent element. Furthermore, the patch also replaces a couple of loops that're used to delete all elements under a node with simply overwriting the contents directly (a pattern already used throughout the viewer). See also: - https://developer.mozilla.org/en-US/docs/Web/API/Node/removeChild - https://developer.mozilla.org/en-US/docs/Web/API/Element/remove	2021-11-16 17:52:50 +01:00
..
chromium	Replace the remaining `Node.removeChild()` instances with `Element.remove()`	2021-11-16 17:52:50 +01:00
firefox	Re-factor the default preferences generation to support build targets (PR 10548)	2021-03-20 11:50:48 +01:00

Jonas Jenwald 4ef1a129fa Replace the remaining Node.removeChild() instances with Element.remove()

Using `Element.remove()` is a slightly more compact way of removing an element, since you no longer need to explicitly find/use its parent element.
Furthermore, the patch also replaces a couple of loops that're used to delete all elements under a node with simply overwriting the contents directly (a pattern already used throughout the viewer).

See also:
 - https://developer.mozilla.org/en-US/docs/Web/API/Node/removeChild
 - https://developer.mozilla.org/en-US/docs/Web/API/Element/remove

2021-11-16 17:52:50 +01:00

chromium Replace the remaining Node.removeChild() instances with Element.remove() 2021-11-16 17:52:50 +01:00

firefox Re-factor the default preferences generation to support build targets (PR 10548) 2021-03-20 11:50:48 +01:00