- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Sep 2022 20:44:43 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Testing support of partial implementations`. <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Testing support of partial implementations<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/3559<br> <fantasai> astearns: Sebastien added some comments, unable to join in person<br> <fantasai> astearns: he has a specific suggestion ...<br> <astearns> this comment https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1114545949<br> <fantasai> rachelandrew: This came uporiginally because of the gap property<br> <fantasai> rachelandrew: originally defined for grid layout, later expanded to flexbox<br> <fantasai> rachelandrew: but can't test within @supports<br> <fantasai> rachelandrew: so can't e.g. provide a fallback margin<br> <fantasai> rachelandrew: unsure where it will come up win future, but for specs like alignment which applie to lots of things could come up<br> <fantasai> rachelandrew: so that's why opened the issue, for testing whether property X roks in context Y<br> <fantasai> s/roks/works/<br> <fantasai> rachelandrew: Idk how likely it is to appear in the future<br> <astearns> ack fantasai<br> <Zakim> fantasai, you wanted to ask to review use cases and to<br> <fantasai> fantasai: Another context is alignment properties applying to abspos or block containers<br> <chris> rssagent, here<br> <fantasai> fantasai: and fremy had suggested gap applying to tables, so that's another place<br> <chris> rrsagent, here<br> <RRSAgent> See https://www.w3.org/2022/09/16-css-irc#T20-38-42<br> <fantasai> astearns: we have general issue of interactions that are difficult to test<br> <fantasai> astearns: sebastian had specific suggestion of allowing custom support rules<br> <fantasai> astearns: that would run author JS to check for a particular thing they wan'ted to test<br> <fantasai> astearns: sebastian asked whether this is a reasonable way forward, is it possible in browsers<br> <fantasai> heycam: No real obvious time to run that script<br> <fantasai> heycam: would want to run it only once<br> <fantasai> heycam: maybe at the time the stylesheet is loaded could run it?<br> <fantasai> heycam: it feels weird to have some script run at some point for that<br> <fantasai> heycam: I do feel like you do want a traditional feature-testing way of checking this<br> <fantasai> heycam: e.g. test whether gap on table, checking whether it has some effect on the size of the element<br> <fantasai> heycam: but idk what's a concise way to run that in a query string<br> <heycam> fantasai: so far most of these are dependent on your formatting context or box type<br> <TabAtkins> q+<br> <heycam> ... so it's not that you want to check interactions with other properties, but specifically whether properties apply to specific types of boxes<br> <astearns> ack TabAtkins<br> <fantasai> TabAtkins: On subject of well-defined time to run, this is the same problem as wanting custom MQ<br> <fantasai> TabAtkins: so we could just run it on that<br> <fantasai> TabAtkins: no difference between writing @media --flex-gap<br> <fantasai> TabAtkins: which you set at page load<br> <fantasai> TabAtkins: vs in supports<br> <fantasai> TabAtkins: if we feel it's needed for usability, maybe separate registry<br> <fantasai> TabAtkins: but run script once and run well-defined time, already have proposal to solve<br> <heycam> fantasai: for the usability aspect of it, there's been proposals of a generic if statement<br> <heycam> ... rather than having custom MQs, you could have a more generic syntax in an if statement<br> <astearns> ack fantasai<br> <heycam> ... so you could do it in a MQ, or in an if<br> <fantasai> s/if statement/@if statement/<br> <fantasai> astearns: Maybe this is enough feedback to satisfy for now?<br> <fantasai> astearns: anyone else to weigh in?<br> <fantasai> dholbert: curious what DOM these queries run in<br> <fantasai> dholbert: does it persist<br> <fantasai> TabAtkins: answer is, dependes on what you are talking about<br> <fantasai> TabAtkins: if you're doing custom MQ, it's whatever you want. YOu're just running JS and updating a map<br> <fantasai> TabAtkins: that's attached to the document object<br> <fantasai> TabAtkins: that'll be available to any stylesheets attached to that page<br> <fantasai> TabAtkins: if doing something else, depends on specifics<br> <fantasai> astearns: let's leave this issue here, and see if we make more progress in issue itself<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1249795176 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 September 2022 20:44:45 UTC