- From: Patrick Dark via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Oct 2018 20:27:21 +0000
- To: public-css-archive@w3.org
@zcorpan Ugh. A `legend`'s default behavior is conditioned on unrelated CSS properties? What a mess. There's always `first-of-type-in-flow(html|legend)`, though I guess the whole proposal won't work either in light of @tabatkins comment. @tabatkins I got the impression from last week's minutes that some think the switch *should* be generalizable which is why this issue has gone back to the drawing board. Perhaps a `legend: none` declaration would be more palatable if it were renamed to something like `legacy-override: fieldset-legend`. That's more generalizable while functionally still just a switch. Another solution is to just fork the element and create something like `fieldgroup`. That'll be several years of polyfills to get behavior like `<fieldset disabled=""/>`, but there won't be any style baggage. -- GitHub Notification of comment by patrickdark Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3094#issuecomment-434066442 using your GitHub account
Received on Monday, 29 October 2018 20:27:28 UTC