- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2022 18:00:51 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-tables] Allow 'order' on table columns`, and agreed to the following: * `RESOLUTION: Close the issue. Lack of interest.` * `RESOLVED: Close the issue. Lack of interest.` <details><summary>The full IRC log of that discussion</summary> <Rossen_> q?<br> <Rossen_> ack jensimmons<br> <JakeA> my bad, I thought we'd moved to another issue<br> <fantasai> fantasai: question is whether to ask fremy to draft up a specific proposal for applying order to tables<br> <fantasai> fantasai: would be restricted within boundaries of a rowspan/colspan, can't shuffle those, but in any case we need a detailed proposal<br> <fantasai> fantasai: and question to WG is do we want a detailed propsoal<br> <Rossen_> q?<br> <fremy> q+<br> <smfr> q+<br> <fantasai> -> https://github.com/w3c/csswg-drafts/issues/7340#issuecomment-1247390415<br> <JakeA> Rossen_: opinons?<br> <Rossen_> ack fremy<br> <JakeA> fremy: I think it's a good time to think about it. I'll spend time in December working it - eg the table spec & this<br> <JakeA> fremy: I think I agree. It doesn't feel like a huge amount of work<br> <JakeA> fremy: I think this is a reasonable thing to do<br> <Rossen_> ack smfr<br> <JakeA> smfr: I think webkit has a low level of enthusiasm to do this.<br> <PaulG> q+<br> <dholbert> +1 to smfr, I have the same feeling RE Gecko's table code<br> <JakeA> smfr: col order has semantic value. I don't think we'd implement this any time soon.<br> <Rossen_> ack PaulG<br> <JakeA> PaulG: MS's spec for focus groups may be impacted by this<br> <Rossen_> q?<br> <JakeA> PaulG: Different things may be correct depending on perspective<br> <iank_> q+<br> <JakeA> Rossen_: I see similar reservation from Mozilla<br> <Rossen_> ack iank_<br> <JakeA> iank_: Q: Would this logic be pre or post col sizing?<br> <JakeA> fremy: Before I guess<br> <JakeA> iank_: We have the newest impl right now. Our proposal would be fine. Table code is tricky due to legacy.<br> <JakeA> iank_: eg how do mergeable columns work? If it's like the order prop in grid & flex, that's simpler<br> <JakeA> iank_: If it's pre sizing, it may have unintended effects on space distribution<br> <JakeA> iank_: If there's a simple way that's clean, that would be fine<br> <JakeA> iank_: tables are complicated :D<br> <JakeA> fremy: Can we move this to tables 4? That gives time for folks to reconsider. Does that make sense?<br> <JakeA> iank_: That's fine by me<br> <JakeA> Rossen_: Freshness of impl doesn't impact complexity due to legacy behaviour.<br> <JakeA> Rossen_: Let's put it on the backlog. Deal with it later.<br> <JakeA> Rossen_: Legacy things aren't going to be removed before then<br> <JakeA> Rossen_: if anyone wants to reopen it, we can<br> <JakeA> fantasai: we can reconsider it in the next level<br> <JakeA> (not 100% I heard the above correctly)<br> <JakeA> fantasai: the problem with closing it is it falls off the radar, and we lose context.<br> <JakeA> jensimmons: What's the usecase? We want to reorder the table without impacting the semantic order?<br> <JakeA> Rossen_: That's exactly where there's pushback. I'm in favour of closing. Objections?<br> <JakeA> Rossen_: Sorry, resolution? It's not a path forward we want to adopt<br> <JakeA> Rossen_: Hearing no objections. Let's close it, and not generate activities on it, that won't have impact.<br> <jensimmons> Giving authors a way to more easily reorder columns & rows is something the web should do! But not in CSS.<br> <fantasai> s/context/context, if we don't want to actually reject it we should defer rather than closing/<br> <JakeA> RESOLUTION: Close the issue. Lack of interest.<br> <fremy> @ jensimmons, I think I agree<br> <astearns> RESOLVED: Close the issue. Lack of interest.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7340#issuecomment-1332541243 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 November 2022 18:00:53 UTC