- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Sep 2018 21:17:20 +0000
- To: public-css-archive@w3.org
@fantasai > `display: legend grid`. I did say it should be an outer display type, that implies you can combine it with an inner one like grid or flex. :) `display` isn't a good fit for legends because it shouldn't actually change the box type. The only thing it should do is to position it in a special way. `position:legend` would be semantically more correct IMO. In both cases though, you'd need to compute it specially (as you suggested for fieldset), since we don't want `<legend style="display:block">` (or `<legend style="position:relative">`) to reset its legendness. In any case, your counter-proposal hinges on a non-existent `appearance:none|auto` property. We already tried to implement that in Gecko per CSS-UI only to have to backout the code after we found that it wasn't web-compatible. To be clear, I will object to implementing `appearance:none|auto` again in Gecko until WebKit/Blink has already **shipped** such a feature **successfully** to prove that it's web-compatible. I think it's rather pointless to discuss a fieldset/legend proposal that builds on a feature that (so far) isn't web-compatible. That said, we could make `-webkit-appearance:fieldset` and `legend:auto` affect the computed `display` value as you suggest. I just think that's unnecessarily complicated compared to letting those properties affect box construction directly with "behaves as" as currently drafted. -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3094#issuecomment-420801027 using your GitHub account
Received on Wednesday, 12 September 2018 21:17:22 UTC