- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 May 2019 00:33:21 +0000
- To: public-css-archive@w3.org
@FremyCompany While I get the worry, I'm not sure if this is something that should block on - especially since it is already available in JS, not only in RO but also in regular JS where this same scenario can occur. I'm fine trying to hone in some type of capability to further restrict RO so that it avoids un-necessary firings, such as recommended in #3663 which I believe is similar to what @mtom55 is stating regarding ranges. This also similar to threshold's in IO, again something an author can have firing numerous times depending on the setup of the page, how many observers are created, etc - and positioning which can adjust based on the same things you've denoted. I'm personally kind of tired (as you know since we worked right next to each other for so long) of this being punted on, especially since we have this in JS and it's effectively syntactic sugar at this point if you build it on top of resizeObserver. I'm open to suggestions so if you have some please let me know. -- GitHub Notification of comment by gregwhitworth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3852#issuecomment-493806192 using your GitHub account
Received on Monday, 20 May 2019 00:33:23 UTC