ResizeObserver is the preferred tool for dynamically responding to element size changes. It can accurately monitor the width, height and box model changes of DOM elements without causing re-arrangement, and it is more efficient to use asynchronous callbacks. Compared with the window.resize event only responds to window changes, ResizeObserver supports observing specific elements, which is suitable for scenes such as lazy image loading, dynamic component rendering, chart container adjustment, and pop-up window positioning. The usage process includes: 1. Create an instance and define a callback; 2. Select the target element; 3. Call observe() to start listening; you can stop listening through unobserve(). Be careful to avoid synchronization operations, circular references, compatibility issues and excessive use.
If you need to respond dynamically to element size changes when developing web pages, instead of relying on window size resize events ( resize
), then ResizeObserver
is the tool you should master. It can directly monitor the size changes of any DOM element, which is more efficient and accurate than polling or triggering reordering.

Why use ResizeObserver?
The traditional approach is to listen for window.resize
events, but this only applies to changes in the entire window and is powerless to change the size of a specific element in the page. Using ResizeObserver
, you can accurately observe changes in size of one or more DOM elements, including width, height, and even box model.
In addition, it does not trigger reorders or triggers frequently, but adopts an asynchronous callback mechanism, which is more performance-friendly.

How to use ResizeObserver
The basic process of using ResizeObserver
is as follows:
- Create an observer instance
- Define callback functions to handle size changes
- Start observing the target element
const observer = new ResizeObserver(entries => { for (let entry of entries) { console.log('Element width and height:', entry.contentRect.width, entry.contentRect.height); } }); const target = document.querySelector('#my-element'); observer.observe(target);
Note:
contentRect
returns the size of the element content area, and does not contain borders and scroll bars. If you need more complete size information, you can combineentry.borderBoxSize
orentry.contentBoxSize
to get it.
If you want to stop listening, just call unobserve()
method:
observer.unobserve(target);
Common application scenarios
Lazy image loading or adaptive layout
When a container size changes, it may be necessary to recalculate how the internal image is displayed, such as switching high-definition images or changing the cropping ratio.
Dynamic component rendering
For example, components in React/Vue can automatically switch presentation modes (such as mobile view/desktop view) based on the parent container size.
Table or chart container adjustment
Some data visualization libraries (such as ECharts) use ResizeObserver
to automatically repaint charts when container changes.
Tooltips or pop-up positioning
When the size of the reference element of the pop-up layer changes, it may be necessary to recalculate the position to avoid misalignment.
Things to note in use
Although ResizeObserver
is very powerful, there are several places that are easy to get stuck in:
- Don't do too many synchronous operations inside : because it is an asynchronous callback, frequent execution of complex logic will affect performance.
- Avoid circular references : For example, if you modify the style of the observed element in the callback and trigger a new resize, it may lead to a dead loop.
- Compatibility issues : Mainstream browsers are supported, but are not available in IE11 and earlier. If you have old browser requirements, you need to introduce polyfill.
- It is okay to observe multiple elements, but don't abuse it : observing large numbers of elements may bring performance overhead, and it is recommended to enable it as needed and clean it up in time.
Basically that's it. After mastering ResizeObserver
, you will find that many layout response problems that were difficult to solve before can be elegantly solved.
The above is the detailed content of Exploring the JavaScript ResizeObserver API. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

JavaScript's garbage collection mechanism automatically manages memory through a tag-clearing algorithm to reduce the risk of memory leakage. The engine traverses and marks the active object from the root object, and unmarked is treated as garbage and cleared. For example, when the object is no longer referenced (such as setting the variable to null), it will be released in the next round of recycling. Common causes of memory leaks include: ① Uncleared timers or event listeners; ② References to external variables in closures; ③ Global variables continue to hold a large amount of data. The V8 engine optimizes recycling efficiency through strategies such as generational recycling, incremental marking, parallel/concurrent recycling, and reduces the main thread blocking time. During development, unnecessary global references should be avoided and object associations should be promptly decorated to improve performance and stability.

There are three common ways to initiate HTTP requests in Node.js: use built-in modules, axios, and node-fetch. 1. Use the built-in http/https module without dependencies, which is suitable for basic scenarios, but requires manual processing of data stitching and error monitoring, such as using https.get() to obtain data or send POST requests through .write(); 2.axios is a third-party library based on Promise. It has concise syntax and powerful functions, supports async/await, automatic JSON conversion, interceptor, etc. It is recommended to simplify asynchronous request operations; 3.node-fetch provides a style similar to browser fetch, based on Promise and simple syntax

JavaScript data types are divided into primitive types and reference types. Primitive types include string, number, boolean, null, undefined, and symbol. The values are immutable and copies are copied when assigning values, so they do not affect each other; reference types such as objects, arrays and functions store memory addresses, and variables pointing to the same object will affect each other. Typeof and instanceof can be used to determine types, but pay attention to the historical issues of typeofnull. Understanding these two types of differences can help write more stable and reliable code.

Hello, JavaScript developers! Welcome to this week's JavaScript news! This week we will focus on: Oracle's trademark dispute with Deno, new JavaScript time objects are supported by browsers, Google Chrome updates, and some powerful developer tools. Let's get started! Oracle's trademark dispute with Deno Oracle's attempt to register a "JavaScript" trademark has caused controversy. Ryan Dahl, the creator of Node.js and Deno, has filed a petition to cancel the trademark, and he believes that JavaScript is an open standard and should not be used by Oracle

Which JavaScript framework is the best choice? The answer is to choose the most suitable one according to your needs. 1.React is flexible and free, suitable for medium and large projects that require high customization and team architecture capabilities; 2. Angular provides complete solutions, suitable for enterprise-level applications and long-term maintenance; 3. Vue is easy to use, suitable for small and medium-sized projects or rapid development. In addition, whether there is an existing technology stack, team size, project life cycle and whether SSR is needed are also important factors in choosing a framework. In short, there is no absolutely the best framework, the best choice is the one that suits your needs.

IIFE (ImmediatelyInvokedFunctionExpression) is a function expression executed immediately after definition, used to isolate variables and avoid contaminating global scope. It is called by wrapping the function in parentheses to make it an expression and a pair of brackets immediately followed by it, such as (function(){/code/})();. Its core uses include: 1. Avoid variable conflicts and prevent duplication of naming between multiple scripts; 2. Create a private scope to make the internal variables invisible; 3. Modular code to facilitate initialization without exposing too many variables. Common writing methods include versions passed with parameters and versions of ES6 arrow function, but note that expressions and ties must be used.

Promise is the core mechanism for handling asynchronous operations in JavaScript. Understanding chain calls, error handling and combiners is the key to mastering their applications. 1. The chain call returns a new Promise through .then() to realize asynchronous process concatenation. Each .then() receives the previous result and can return a value or a Promise; 2. Error handling should use .catch() to catch exceptions to avoid silent failures, and can return the default value in catch to continue the process; 3. Combinators such as Promise.all() (successfully successful only after all success), Promise.race() (the first completion is returned) and Promise.allSettled() (waiting for all completions)

CacheAPI is a tool provided by the browser to cache network requests, which is often used in conjunction with ServiceWorker to improve website performance and offline experience. 1. It allows developers to manually store resources such as scripts, style sheets, pictures, etc.; 2. It can match cache responses according to requests; 3. It supports deleting specific caches or clearing the entire cache; 4. It can implement cache priority or network priority strategies through ServiceWorker listening to fetch events; 5. It is often used for offline support, speed up repeated access speed, preloading key resources and background update content; 6. When using it, you need to pay attention to cache version control, storage restrictions and the difference from HTTP caching mechanism.
