- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Apr 2020 16:38:41 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `editorial: Paint Containment description is incomprehensible`, and agreed to the following: * `RESOLVED: Accept the comment at the end of https://github.com/w3c/csswg-drafts/issues/4946#issuecomment-614501289` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: editorial: Paint Containment description is incomprehensible<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4946<br> <miriam> thanks! :)<br> <dael> florian: Matts has found there's places we're vague and non-standard. First is we mention things that must be clipped include content and paint and geometry of desc. Not defined terms. I think it was ink and scrollable overflow<br> <dael> florian: Should replace the phrasing<br> <dael> TabAtkins: Yeah<br> <faceless2> @orial awful for me too<br> <dael> florian: Second part is in a note we say as if overflow-visible was changed to overflow clip as used value. Prop we replace with [reads]<br> <dael> florian: I'll tweak to be explicit about overflow-x and -y in case it's different values<br> <dael> Rossen___: Sounds great<br> <dael> smfr: Is scrollable overflow defined?<br> <dael> florian: Yes<br> <dael> smfr: descendants you need to be clear paint order? containing block?<br> <fantasai> smfr, definitions of overflow: https://www.w3.org/TR/css-overflow-3/#overflow-concepts<br> <dael> smfr: I mean z order descendants. Stacking context<br> <dael> florian: If we mean all do we need to disambig?<br> <chris> +1 to smfr say which tree they are descendants in<br> <dael> smfr: All is unclear. dom node? A child can break out if position abs. I may not paint as desc if it has z-index<br> <dael> florian: I think we're talking about all starting from dom. Weither positioned or painted they're part of all<br> <dael> smfr: THan have to create containing for positioned and stacking<br> <dael> florian: THink it does<br> <fantasai> https://drafts.csswg.org/css-contain-1/#containment-paint<br> <dael> smfr: And containing block for fixed?<br> <dael> dbaron: Does for fixed and abs and stacking contexts. Bullets 2 & 3<br> <dbaron> in https://drafts.csswg.org/css-contain/#containment-paint<br> <dael> Rossen___: Any other questions or opinions or good to resolve?<br> <dael> florian: One question. Correct phase to say all descendants? All DOM?<br> <dael> fantasai: All ambig reasolves to same thing doesn't matter.<br> <dael> florian: We have later bullets to say if it's all it works.<br> <dael> fantasai: What's interp that doesn't mean all? ambig can't resolve to anything that's not what you meant so it doesn't matter<br> <dael> smfr: It's fine<br> <Rossen___> https://github.com/w3c/csswg-drafts/issues/4946#issuecomment-614501289<br> <dael> Rossen___: Objections to proposal here ^<br> <dael> florian: Prop: Accept the comment at the end of https://github.com/w3c/csswg-drafts/issues/4946#issuecomment-614501289<br> <dael> RESOLVED: Accept the comment at the end of https://github.com/w3c/csswg-drafts/issues/4946#issuecomment-614501289<br> <dael> fantasai: Want to resolve to update recommendation?<br> <dael> Rossen___: This is WD<br> <dael> florian: L1 is a rec<br> <dael> florian: L2 is a WD, but L1 is rec and phrase is in both<br> <dael> Rossen___: oooh<br> <dael> chris: Should be an erratum. Are there any others we can roll in to a publish?<br> <dael> florian: I need to check<br> <dael> florian: Let's move on with agenda and I'll get back about if there are more in the queue<br> <AmeliaBR> No errata for contain 1: https://www.w3.org/Style/2019/REC-css-contain-1-20191121-errata.html<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4946#issuecomment-617892686 using your GitHub account
Received on Wednesday, 22 April 2020 16:38:43 UTC