- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Oct 2024 17:02:54 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[cssom-view] Expose small/large viewport dimensions of the layout viewport`, and agreed to the following: * `RESOLVED: We will expose large/small/dynamic objects representing the layout viewport sizes as accessors with width/height/block/inline properties; details and which object TBD` <details><summary>The full IRC log of that discussion</summary> <fantasai> ydaniv: Already resolved to export viewport object that exposes the properties you can read regarding the layout viewport<br> <fantasai> ydaniv: on that object proposal is to expose large/small/dynamic accessors<br> <fantasai> ydaniv: for the widht/height/block/inline properties<br> <fantasai> ydaniv: so that developers can read those in JS<br> <fantasai> smfr: Are these live? do they change when you scroll?<br> <fantasai> fantasai: small/large are static... dynamic changes<br> <fantasai> smfr: but position changes?<br> <fantasai> fantasai: only exposes size, not position<br> <fantasai> smfr: Do we fire an event when dynamic size changes?<br> <fantasai> ydaniv: I think we already have those<br> <fantasai> ydaniv: that's the resize event<br> <fantasai> ydaniv: visual viewport exposes events, no proposal here to make this also an event target<br> <emilio> q+<br> <fantasai> smfr: ok<br> <fantasai> smfr: not sure about the timing of dynamic viewport change and event firing, might not be accurate<br> <astearns> ack emilio<br> <fantasai> emilio: This is not ? to the visual viewport resize<br> <fantasai> s/?/equivalent/<br> <fantasai> emilio: the visual viewport size, I don't think it changes with the dynamic viewport<br> <fantasai> emilio: changes when zooming in and out<br> <fantasai> astearns: so continue discussing, or resolve on adding large/small/dynamic objects to window?<br> <fantasai> smfr: Slightly concerned about .viewport being confused with visual viewport<br> <fantasai> emilio: but that's a different discussion<br> <fantasai> smfr: exposing these somehwere, just unsure where<br> <emilio> q+<br> <fantasai> PROPOSED: We will expose large/small/dynamic as accessors with width/height/block/inline properties; TBD on which object<br> <fantasai> ydaniv: could also resolve on makign this the layout viewport<br> <fantasai> ydaniv: other than naming, don't think there's an objection<br> <astearns> ack emilio<br> <fantasai> PROPOSED: We will expose large/small/dynamic objects representing the layout viewport sizes as accessors with width/height/block/inline properties; TBD on which object<br> <fantasai> PROPOSED: We will expose large/small/dynamic objects representing the layout viewport sizes as accessors with width/height/block/inline properties; details and which object TBD<br> <fantasai> RESOLVED: We will expose large/small/dynamic objects representing the layout viewport sizes as accessors with width/height/block/inline properties; details and which object TBD<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8709#issuecomment-2402852401 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 October 2024 17:02:55 UTC