The ResizeObserver has an observe() method and an unobserve() method. This seems to encourage having one ResizeObserver instance and observing and unobserving different elements as needed with logic in the callback to handle each entity. Is there any performance implications of doing this vs instantiating multiple ResizeObservers for observing different elements or groups of elements?

The ResizeObserver has an observe() method and an unobserve() method. This seems to encourage having one ResizeObserver instance and observing and unobserving different elements as needed with logic in the callback to handle each entity. Is there any performance implications of doing this vs instantiating multiple ResizeObservers for observing different elements or groups of elements?

• javascript

Share Improve this question Follow asked Jul 25, 2018 at 23:18 Wilhelmina LohanWilhelmina Lohan 3,04333 gold badges3232 silver badges6565 bronze badges 2

• the unobserve method isn't encouraging reuse of a resize observer. It's a neccesity to allow proper garbage collection of listeners and elements – bryan60 Commented Jul 25, 2018 at 23:43
• Like the MutationObserver, disconnect() can be used for garbage collection. – Wilhelmina Lohan Commented Jul 26, 2018 at 14:55

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 11

Looks like reusing (one) the ResizeObserver is preferred and more preformant:

https://github./WICG/ResizeObserver/issues/59#issuement-408098151 https://groups.google./a/chromium/forum/#!msg/blink-dev/z6ienONUb5A/F5-VcUZtBAAJ