- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Jun 2021 16:34:00 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `cssom-view`, and agreed to the following: * `RESOLVED: Incorporate visualViewport into cssom-view and add bokand as editor` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: cssom-view<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6339<br> <TabAtkins> https://wicg.github.io/visual-viewport/index.html<br> <fantasai> TabAtkins: Visual Viewport spec that allows getting bounds of visual viewport in JS<br> <fantasai> TabAtkins: has been implemented cross-browser for awhile<br> <fantasai> TabAtkins: probably should be on standards-track<br> <fantasai> TabAtkins: suggestion is to put into cssom-view<br> <fremy> LGTM<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: Who's the editor?<br> <fremy> fantasai: who is gonna be editor?<br> <fantasai> TabAtkins: bokan is editor of visual viewport spec... and is a member of CSSWG<br> <fantasai> TabAtkins: could just add him<br> <fantasai> smfr: Emilio and I are editors of CSSOM-view, and would appreciate editorial help<br> <fremy> fantasai: sounds like a good idea to have one more person on this<br> <fantasai> TabAtkins: chrishtr, can we volunteer bokand?<br> <fantasai> chrishtr: We can try, and if he's busy, we'll find somone else on our staff<br> <fantasai> astearns: so propose to incorporate visualViewport into cssom-view and add bokand as editor<br> <fantasai> RESOLVED: Incorporate visualViewport into cssom-view and add bokand as editor<br> <fremy> welcome to the css family, new spec :)<br> <fremy> fantasai: one more comment<br> <fremy> fantasai: it's a bit weird how things happened here<br> <fremy> fantasai: we are not doing standardization, we are doing documentation<br> <fremy> fantasai: I don't find this workflow appropriate<br> <fremy> fantasai: so I agree to do it here, but it's worth nothing I think it is not a good workflow<br> <fantasai> fantasai: It's too late to make any changes now, so what's the point of putting in a "standardization" process<br> <fremy> astearns: I agree<br> <fremy> astearns: that said, it happens, and we can't change it<br> <fremy> astearns: and documentation is still good<br> <fremy> TabAtkins: also, it shipped in multiple browsers<br> <fremy> TabAtkins: discussion happened, in another venue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6339#issuecomment-862529944 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 June 2021 16:34:24 UTC