Re: [css-houdini-drafts] [css-layout-api] Should display: layout(x) work on any element?

The Houdini Task Force just discussed `Should layout() apply to every element?`, and agreed to the following:

* `RESOLVED: display:layout() works on fieldset, same as display:grid or display:flexbox do. (It applies to the inner box, and does not lay out the rendered legend.)`
* `RESOLVED: Publish a new version of the WD`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> Topic: Should layout() apply to every element?<br>
&lt;emilio> Github: https://github.com/w3c/css-houdini-drafts/issues/796<br>
&lt;emilio> TabAtkins: If display works on an element it display: layout() should work<br>
&lt;emilio> cbiesinger: There's a bunch of requests to make display work on fieldsets<br>
&lt;emilio> TabAtkins: at which point layout() should work<br>
&lt;emilio> emilio: fieldset display is weird because it only affects the display of the anonymous block inside it, at least on Gecko<br>
&lt;TabAtkins> TabAtkins: So the "inner" display values work, just not the outer ones. (no block/inline, but flex/grid is fine)<br>
&lt;TabAtkins> layout() is an "inner" display value.<br>
&lt;TabAtkins> So it should work.<br>
&lt;emilio> emilio: should you call layout() on the legend?<br>
&lt;emilio> TabAtkins: I'm happy to say legend is outside of your rendering, and that layout() is called for the contents of your inner box<br>
&lt;emilio> Rossen: so is the resolution that display layout() should work on any element that accepts a display value?<br>
&lt;emilio> emilio: what about replaced?<br>
&lt;rego> JFYI, "display: grid" on &lt;fieldset> works in Firefox, Safari, Edge but not in Chromium<br>
&lt;TabAtkins> (Because that's consistent with the behavior of dipslay:grid on it; it only lays out the inner box, which doesn't include the &lt;legend>)<br>
&lt;emilio> TabAtkins: it only honors the outer display value, like setting display: grid on an image you just get a block<br>
&lt;emilio> emilio: what outer display does layout() have? block?<br>
&lt;emilio> TabAtkins: yeah, thought we may want to add inline-layout() to handle that<br>
&lt;emilio> heycam: so display: layout() for an svg doesn't apply right?<br>
&lt;emilio> TabAtkins: hmm, so svg elements do honor display none... needs a bit better definition<br>
&lt;emilio> iank_: so it's not a layout-api issue right?<br>
&lt;emilio> TabAtkins: no, css-display<br>
&lt;TabAtkins> (or the theoretical svg-layout spec I've been threatening to write for a few years)<br>
&lt;emilio> Rossen: so... We have a resolution?<br>
&lt;emilio> TabAtkins: proposal: should work on fieldset<br>
&lt;emilio> Rossen: the title seemed a bit more general<br>
&lt;emilio> TabAtkins: I think except svg, fieldset is the only really special thing<br>
&lt;TabAtkins> Proposed resolution: display:layout() works on fieldset, same as display:grid or display:flexbox do. (It applies to the inner box, and does not lay out the rendered legend.)<br>
&lt;emilio> RESOLVED: display:layout() works on fieldset, same as display:grid or display:flexbox do. (It applies to the inner box, and does not lay out the rendered legend.)<br>
&lt;emilio> Rossen: other issues?<br>
&lt;emilio> iank_: nope<br>
&lt;emilio> RESOLVED: Publish a new version of the WD<br>
&lt;emilio> bkardell_: I'm wondering how much effort we're spending into throttled network stuff, or other way the developer could apply layout when loads are slow and such?<br>
&lt;bkardell_> s/bkardell_/philipwalton<br>
&lt;emilio> iank_: The promise return from the module load... You can use that when all the JS stuff loaded there is done<br>
&lt;emilio> iank_: But it'd be interesting to have something like font loading works<br>
&lt;emilio> iank_: I think we need to be able to load worklets declaratively<br>
&lt;emilio> iank_: there has been talk in the past of a top level promise to the document<br>
&lt;emilio> iank_: which it may be useful to allow people to wait for critical parts of the UI and such<br>
&lt;emilio> iank_: but that's a separate discussion<br>
&lt;emilio> philipwalton: is there an issue for that?<br>
&lt;emilio> iank_: if you could file it'd be great<br>
&lt;emilio> TabAtkins: we definitely need to talk to the preload people to be able to load modules<br>
&lt;emilio> iank_: and the TAG should probably be involved yeah<br>
&lt;TabAtkins> &lt;br dur=20min><br>
&lt;emilio> Rossen: So that's all for layout, let's take a break and do typed OM when back<br>
</details>


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

Received on Thursday, 25 October 2018 08:23:18 UTC