- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Sep 2022 20:52:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-align-3] Baselines need to be defined on fieldsets.`, and agreed to the following: * `RESOLVED: default first and last baselines to be the fieldset content's` <details><summary>The full IRC log of that discussion</summary> <astearns> topic: [css-align-3] Baselines need to be defined on fieldsets.<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/7656<br> <emilio> ScribeNick: emilio<br> <emilio> iank_: fieldsets need their baseline defined<br> <emilio> ... they're special, have a <legend> on the border area<br> <emilio> ... and their contents are wrap in a box with arbitrary display type<br> <iank_> https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=10714<br> <emilio> iank_: implementations do wild things<br> <emilio> ... dgrogan has screenshots of what browsers do today<br> <emilio> ... my preference is to ignore the legend<br> <emilio> ... that's Chromium's behavior<br> <emilio> fantasai: I'd like to argue for Safari's behavior<br> <emilio> ... first baseline from legend, last from content<br> <emilio> Rossen_: why is that more sensible?<br> <emilio> fantasai: legend is the first bit of text that you see<br> <emilio> ... seems reasonable to align to it<br> <emilio> ... that should def. work<br> <fremy> +1 for aligning fieldsets with each other based on the legend<br> <emilio> ... not sure what the last baseline to be, but taking the last baseline of the content of the fieldset makes sense to me<br> <emilio> iank_: I think I disagree, <legend> is like table captions<br> <emilio> ... they have smaller font-size, they're not the main content of the fieldset<br> <emilio> ... first baseline should be actual content, that makes more sense to me<br> <emilio> fantasai: would be great if web designers would weigh in on this<br> <emilio> Rossen_: one potential use case might be aligning multiple fieldsets<br> <emilio> iank_: aligning to non-fieldset content is more common I think<br> <emilio> dbaron: I think I lean towards agreeing with iank_<br> <Rossen_> ack dbaron<br> <emilio> ... not that uncommon for fieldsets to lack a <legend><br> <miriam> +1 Ian and David<br> <emilio> ... if we wanted to align to legend we'd need to define what happens when there's no legend<br> <emilio> +1<br> <tantek> +1<br> <heycam> q+<br> <emilio> ... my sense is that it's common not to have one<br> <Rossen_> ack heycam<br> <emilio> iank_: if you're aligning fieldsets with and without legends it'd be weird<br> <emilio> heycam: agree with iank_ as well, legend is ancillary content like captions<br> <emilio> ... fieldset legend could also have multiple lines of text as well<br> <emeyer> q+<br> <Rossen_> ack emeyer<br> <emilio> emeyer: I'm looking at live dom viewer on irc<br> <emilio> ... I accept the argument that aligning to the legend is a bit dangerous<br> <emilio> ... I have the feeling that many fieldsets don't have legend<br> <emilio> ... but I do see situations for all three kinds of alignment. legend/first/last content<br> <emilio> ... if I had to pick one I'd choose first line of contents<br> <emilio> ... but I see use cases for the others<br> <emilio> ... there's cases where I might want to align to others<br> <emilio> ... I think both patterns would be common<br> <emilio> fantasai: when you want first line to align, is there case where the legends don't align?<br> <emilio> q+<br> <zcorpan> q+<br> <emilio> emeyer: I can't think of a reason, I'd want the legends to align with each other<br> <emilio> ... sometimes I want text outside to align with the legend<br> <emilio> iank_: if you want to align legends using top-alignment would work unless there's non-fieldset content<br> <emilio> emeyer: I probably would want the text outside to align with the first line of content rather than the legend<br> <emilio> iank_: we could also add a switch to allow you to align to a legend if that use case comes up<br> <emilio> fantasai: there's an issue to allow choosing baseline alignment box<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/1339<br> <heycam> emilio: I was going to say something related what Ian said. we could add a switch but I'd also like to ignore the legend<br> <Rossen_> ack emilio<br> <heycam> ... if the use case for aligning to a legend comes up often, where you're aligning text outside the fieldset with the legend of the fieldset, which seems odd, we could look to allow that<br> <heycam> ... but seems farfetched<br> <heycam> ... for most cases top alignment should do<br> <Rossen_> ack zcorpan<br> <emilio> zcorpan: we discussed whether there's a case where legends wouldn't be align<br> <emilio> ... if you have a fieldset with one line of text and another when the legend is 2+ lines of text<br> <emilio> ... those wouldn't be necessarily align<br> <emilio> ... depending on what we decide<br> <emilio> ... maybe I misunderstood<br> <astearns> no, I had the same idea<br> <emilio> iank_: that's a similar problem if you try to align a fieldset with a legend and one without<br> <emilio> Rossen_: it sounds the obvious use case is that the first baseline of content needs to be available<br> <emilio> ... we need to resolve to have first-line baseline based on the content<br> <emilio> ... be available. The second question is whether we need to make the legend baseline available<br> <heycam> emilio: I would propose to try resolving the default be the baseline of the content<br> <heycam> ... if there are use cases that can't be solved without the baseline of the legend, work on what fantasai was talking about, choosing the baseline box<br> <emilio> Rossen_: seems to agree with the majority of the +1s and arguments made<br> <zcorpan> +1<br> <emilio> Rossen_: fantasai, objections?<br> <emilio> fantasai: defer to emeyer and jensimmons<br> <emilio> s/fantasai, //<br> <emilio> emeyer: the proposed resolution is to default to first or last baseline of the content?<br> <emilio> emilio: both baselines first and last would be baseline of the content box<br> <emilio> emeyer: feels probably correct, I'll take al look at various cases to confirm it's not a bad idea, but seems like the best resolution<br> <emilio> RESOLVED: default first and last baselines to be the fieldset content's<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7656#issuecomment-1248617134 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 September 2022 20:52:06 UTC