Re: [csswg-drafts] [css-om-view] Describe layout and visual viewports (#4724)

The CSS Working Group just discussed `[css-om-view] Describe layout and visual viewports`, and agreed to the following:

* `RESOLVED: Start defining what we call layout and visual viewport`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-om-view] Describe layout and visual viewports<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4724<br>
&lt;dael> smfr: Rossen_ and I talked offline. I think browser have converserge on mech for fixed post in fac eof page zoom. 2 rectangles layout and visual viewport. Not defined anywhere. WOuld be willing to write text to live in CSSOM View. Asking res to add a section to the spec for the layout and visual viewport. I expect bikeshedding<br>
&lt;dael> Rossen_: I support adding the text. Question- besides describing what it is and does what else is there to be done?<br>
&lt;dael> Rossen_: Don't anticiplate providing units or capabilities that are accessible to css?<br>
&lt;dael> smfr: Right. Think should desc how they interact. When you zoom and scroll some fixedpos will disappear is unexpected for some authors. Spec should explain<br>
&lt;florian> q+<br>
&lt;dael> Rossen_: 100% with you. Wanted to make sure only thing we're doing is adding explination. Not adding capabilities for authors to target<br>
&lt;dael> smfr: Correct<br>
&lt;dael> smfr: There is a viewport API spec which will reference this.<br>
&lt;dael> Rossen_: Link?<br>
&lt;dael> astearns: In issue<br>
&lt;astearns> ack florian<br>
&lt;heycam> +1 on moving towards being able to write down what &lt;meta viewport> does<br>
&lt;dael> florian: I'm supportive of this. For a long time this was intended to be done once anyone had time. All sorts of reference in css to "the viewport" but we have multiple. Eventually we'll need to spec the viewport metatag and a css way to adjust so I suggest write definitions so viewport can be touched eventually<br>
&lt;dael> smfr: Additional wrinkle is we have not spec how scroll position is derived. I think some movement to being around layout viewport, but we should spec that as well<br>
&lt;dael> florian: Need to define the viewports then audit the specs to what they're referring to. This is one of those but I'm sure many more<br>
&lt;dael> Rossen_: Good to remember what constitutes an initial containing block in prsense of these viewports<br>
&lt;dael> Rossen_: For abspos the containing block is layout viewport but for fixed it's visual viewport. That's observable for user<br>
&lt;dael> smfr: Yes. Not sure those viewports are right but yes<br>
&lt;dael> florian: Maybe do this as a series of PRs defining the viewports. Then finding instances of specs where they're referred will take longer. Shouldn't be a single pull request.<br>
&lt;dael> smfr: Correct<br>
&lt;dael> astearns: Prop: Start defining what we call layout and visual viewport<br>
&lt;dael> astearns: I'm hearing consensus. Any concerns or objections?<br>
&lt;dael> florian: Proccedural. If defined in OM View it forces us to have it as a spec that goes to REC. If it's moving makes dependency chain awk.<br>
&lt;dael> astearns: True whereveer they are<br>
&lt;dael> florian: True. We can start there and move if we're blocked<br>
&lt;dael> astearns: Or a L1 with just these. Do you have asuggestion of where else?<br>
&lt;dael> florian: A viewport. Device adaptation originally but it's becoming fiction<br>
&lt;dael> fantasai: We could drop the fiction and focus what's in there. I don't think there's a reason to keep stuff not being impl<br>
&lt;dael> smfr: I would prefer not device adaptation b/c these concepts feel more fund. to basic css. Coordinate systems not just about device adaptation they're fairly fundemental<br>
&lt;dael> astearns: We can hash this out at a later time. Let's get it done and then haggle.<br>
&lt;dael> astearns: Obj?<br>
&lt;fantasai> I'd probably keep coordinate systems in either cssom-view or css-overflow<br>
&lt;dael> RESOLVED: Start defining what we call layout and visual viewport<br>
&lt;fantasai> but layout viewport vs visual viewport is more fundamental than OM<br>
&lt;dael> astearns: Past that we discussed other things we might need to define. Good to have a note saying these things aren't yet defined but likely to come out of this work? So we've got a record of thigns we might get to?<br>
&lt;fantasai> so I think device-adaptation is a better place, if we make it to be more fundamental<br>
&lt;dael> smfr: Sure, happy to add.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4724#issuecomment-582677042 using your GitHub account

Received on Thursday, 6 February 2020 00:22:07 UTC