- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Oct 2024 16:51:00 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `It is unclear which Document object https://drafts.csswg.org/resize-observer/#ref-for-resizeobserver is talking about`, and agreed to the following: * `RESOLVED: ResizeObserver uses the "current" global document` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> emilio: resizeObserver spec doesn't define, when you create an observer, what Document you add it to.<br> <TabAtkins> emilio: that can be different if you do something like iframe.contentWindow.ResizeObserver<br> <chrishtr> +1<br> <TabAtkins> emilio: I think from code comments blink and gecko both use "current" global; I think webkit too. We shoudl spec that.<br> <TabAtkins> TabAtkins: remind me which is "current"?<br> <TabAtkins> emilio: in this case, the iframe<br> <TabAtkins> emilio: the "relevant global" from the ResizeObserver object<br> <astearns> https://html.spec.whatwg.org/multipage/webappapis.html#concept-current-everything<br> <TabAtkins> astearns: you linked to "current" in your comment<br> <TabAtkins> astearns: so i assume you mean *that* current, not "relevant" that follows it<br> <smfr> q+<br> <TabAtkins> emilio: so "relevant" you need an object already. i think it needs to be "current", which would be the iframe document in this case, even if the script is from the outer page<br> <astearns> ack smfr<br> <TabAtkins> smfr: is thsi different from IntersectionObserver? can thtey be specced the same way?<br> <TabAtkins> emilio: they shoudl definitely be consistent, I think IO already uses current<br> <TabAtkins> emilio: I'll check<br> <TabAtkins> astearns: we could resolve to spec what current engines do, and make it consistent with IO<br> <TabAtkins> emilio: ah, i have an issue on IO spec, because it depends on what you observe, per spec, which isn't great<br> <TabAtkins> emilio: I'll crosslink in the issue<br> <TabAtkins> emilio: but wekbit and gecko do use the same concept<br> <TabAtkins> astearns: and you're sure what the concept is?<br> <TabAtkins> emilio: i'm 90% it's "current"<br> <TabAtkins> emilio: the realm that the function you're calling lives in<br> <TabAtkins> astearns: so we can resolve to define that both RO and IO use "current" global document, as long as that reflects reality<br> <TabAtkins> emilio: sounds good<br> <TabAtkins> might not match blink's IO bheavior<br> <TabAtkins> chrishtr: I"ll follow up with Stephan about IO<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: ResizeObserver uses the "current" global document<br> <TabAtkins> (I should raise an issue about fixing these terrible names)<br> <emilio> https://github.com/w3c/IntersectionObserver/issues/525 is IntersectionObserver behavior<br> <emilio> s/behavior/issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10516#issuecomment-2432844692 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 October 2024 16:51:01 UTC