- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jan 2024 00:20:19 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[cssom-view] No event to track window position`, and agreed to the following: * `RESOLVED: PURSUE EVENT TO MAKE REPORTS MORE ERGONOMIC TO USE` <details><summary>The full IRC log of that discussion</summary> <frances_> florian: window attribute has objects and event when size changes but not when position changes, proposal to add move event that works similar to resize event<br> <frances_> florian: nuance while position attribute is on object, browsers are not required to report or have a global coordinate system and hide them, not reliably available<br> <frances_> florian: if not possible to land html patch, might differ things, could possibly land them in css patch<br> <khush> q+<br> <frances_> Alan: Alice's prs are closed why?<br> <frances_> florian: suspected glitch of rebasing, sat for a while and appears closed<br> <astearns> ack khush<br> <frances_> khush: Do all os's have this event? Are we expecting all browsers to behave similarly?<br> <frances_> Florian: fickle to speak of all os's, not finite, up to implementation detail and html loop in rendering, not need to pull more frequently<br> <frances_> florian: theres a limit on how frequently<br> <frances_> khush: if window position is changing, how can we minimize wakeups on the screen and not rely on it in case os is not giving the event<br> <frances_> Alan: possibly resize event has timing specified<br> <frances_> florian: specified similarly<br> <frances_> khush: doubt to have the problem on the os when window is resized<br> <frances_> florian: as mentioned, linux on Wayland does not have os tell changes on coordinates, windows are composited, no requirement to report numbers<br> <frances_> florian: up to implementation discretion, numbers are already exposed<br> <frances_> Alan: Igalia is possibly looking for an okay and no objections to adding the event<br> <frances_> florian: possible limited appetite to the event, make it convenient to not waste energy in actively pulling<br> <frances_> Alan: any other comments or thoughts?<br> <frances_> Daniel: is it set in such a way to detect whether you will ever get a callback or expect it?<br> <frances_> florian: there is nothing on the event itself, possible window attributes maybe undefined<br> <frances_> florian: spec should give an answer<br> <frances_> Daniel: that is my only concerned, sort of imperfect, might not return anything, need to make it ergonomic with the known limitation<br> <frances_> Alan: put something on the spec such as exposing window position and does it get updated, put event on the window object or it shouldn't be there to add the existence of the event<br> <frances_> florian: trying to find part of the spec to find where the information is, spec says you don't have to report. Does anyone remember?<br> <frances_> Alan: these are details that we can work out<br> <frances_> Daniel: Wayland limitation is possibly substantial, might never work it is an important constraint to be aware of<br> <frances_> florian: important on window object itself<br> <frances_> Daniel: we already expose possibly bad information, need to be more ergonomic<br> <frances_> florian: trying to find the part of spec, possibly open separate issue to track and detect<br> <frances_> florian: is it relevant to know difference between 0 0 corner? open issue and track<br> <frances_> Alan: should we land a spec for the event and then ask for a privacy review or vice versa?<br> <frances_> florian: event doesn't make information worse, need to add way to report information with privacy considerations<br> <frances_> Alan: information available but hard to use, might make it detrimented<br> <frances_> florian: might make it inefficient for the programmer<br> <frances_> Ian: trivial, not difficult to access<br> <frances_> Daniel: agreed<br> <vmpstr> this says 0 if not available, not sure if that's the right spot https://drafts.csswg.org/cssom-view/#dom-window-screenleft<br> <frances_> Alan: let's finish up discussion<br> <frances_> RESOLVED: PURSUE EVENT TO MAKE REPORTS MORE ERGONOMIC TO USE<br> <frances_> florian: should pull request wait?<br> <chrishtr> Agree to land a PR<br> <frances_> Alan: pull request then work on detials<br> <frances_> florian: move on css or pursue html request from get go?<br> <frances_> Alan: do both in both specs directly<br> <frances_> florian: agreed<br> <frances_> Alan: no objections<br> <frances_> Alan: next issue. Zoom issues for Chris.<br> <frances_> Alan: issue 9644 on iframes<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7693#issuecomment-1876144667 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 January 2024 00:20:21 UTC