W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2019

Re: [csswg-drafts] [resize-observer] Which box information should we pass to the callback (#3329)

From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
Date: Mon, 25 Feb 2019 19:42:33 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-467154029-1551123752-sysbot+gh@w3.org>
@TremayneChrist We're going to be discussing all of these options today in a breakout session at the CSSWG meeting - all of them will hopefully lead to resolutions for each that are very clear. We'll have clear resolutions (if we get them) by tomorrow EOD in the minutes that get appended via the IRC bot.

> What happens if this occurs?

Regarding your current question - that's a solid one but I would expect it to behave the same as other observers which effectively the latest observer's config. Using mutation observer as an example:

https://jsbin.com/cogusojiwo/edit?html,js,console,output

Here you can see that I am both adding a new element and adding an attribute but the callback only fires on the attribute. So I would expect RO to behave the same way and you would only get an observation of the `content-box` here. Also, you're not going to want to watch numerous boxes of the same element, which is why we removed the capability to pass in an array of boxes to observer as it can lead to an increase of missed events. @atotic just in case RO behaves differently from MutationObserver for some reason.

-- 
GitHub Notification of comment by gregwhitworth
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3329#issuecomment-467154029 using your GitHub account
Received on Monday, 25 February 2019 19:42:34 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:44 UTC