Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Add a resizeend event to the Window #8874

Closed
thegreatercurve opened this issue Feb 10, 2023 · 3 comments
Closed

Proposal: Add a resizeend event to the Window #8874

thegreatercurve opened this issue Feb 10, 2023 · 3 comments

Comments

@thegreatercurve
Copy link

thegreatercurve commented Feb 10, 2023

An experimental scrollend event has recently been added to Firefox and Chrome.

Similarly, I want to propose to add a similar resizeend event to the Window whenever the user has finished resizing the window, whether-or-not via mouse our touch input.

(The resize, scroll and scrollend events are mentioned close together in the current spec).

Listening to this event would look the same as the above as well:

window.addEventListener('resizeend`, event => { ... })

// Or 

window.onresizeend = event => { ... }

The benefits of resizeend would be similar to scrollend in that it removes the need for debouncing or timeouts to try to detect the end of the resize.

CC @argyleink

@smaug----
Copy link
Collaborator

Is the information that user has stopped resizing available on all the OSes? And how would this work, when the resize isn't user initiated but the OS just decides to resize window because of some other reason?

@thegreatercurve
Copy link
Author

Is the information that user has stopped resizing available on all the OSes? And how would this work, when the resize isn't user initiated but the OS just decides to resize window because of some other reason?

@smaug---- It should be available on all devices and OSes, similar to the resize event. Also, there's no awareness about how the resize event is initiated.

@annevk
Copy link
Member

annevk commented Mar 1, 2023

It seems you should file this against CSSOM View Module, not the HTML Standard. (See the top of the document you linked to for where to file the issue.)

@annevk annevk closed this as not planned Won't fix, can't repro, duplicate, stale Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants