W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

Re: [csswg-drafts] Link "Applies to", "Canonical order" in propdef tables (#3827)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Jan 2021 17:54:29 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-763824485-1611165267-sysbot+gh@w3.org>
The CSS Working Group just discussed `Link "Applies to", "Canonical order" in propdef tables`, and agreed to the following:

* `RESOLVED: Fix the draft of cssom so it points to color 4 and then publish`
* `RESOLVED: Publish cascade after resolution of 4838`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Link "Applies to", "Canonical order" in propdef tables<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3827#issuecomment-759849067<br>
&lt;fantasai> https://drafts.csswg.org/css-cascade-4/#changes<br>
&lt;dael> fantasai: Have some text we can link to. Cascade 4 has a nice section of it. Needs to be republished as a WD. Changes here ^ one issue still being discussed so may not be able to publish today<br>
&lt;dael> fantasai: Other major changes we did is define processing of elements not in tree and define term property<br>
&lt;dael> fantasai: Other problem is that canonical order is only defined in cssom editors draft. That's far ahead of tr and it is behind on edits.<br>
&lt;dael> fantasai: In order to crosslink we need to republish cssom. But I don't know state of draft and if it should be published or needs more edits.<br>
&lt;dael> fantasai: We can't make fix to propdef tables as long as spec is out of date<br>
&lt;dael> astearns: emilio do you have an idea of if we could publish cssom draft as is?<br>
&lt;dael> emilio: I think we could publish. A few fixes i'd like but they interact with HTML<br>
&lt;dael> astearns: Could resolve to publish a new WD of cssom as-is?<br>
&lt;dael> TabAtkins: One edit that might be good to pull in which is remove color serialization so we can defer to color 4<br>
&lt;dael> chris: I have removed it. But there's a related issue where it keeps linking to color 3 and I want to stop it. But the edits are in<br>
&lt;dael> astearns: Prop: Fix the draft of cssom so it points to color 4 and then publish<br>
&lt;dael> astearns: Objections?<br>
&lt;chris> +1<br>
&lt;dael> RESOLVED: Fix the draft of cssom so it points to color 4 and then publish<br>
&lt;dael> astearns: What do we want to do on cascade?<br>
&lt;fantasai> https://drafts.csswg.org/css-cascade-4/#changes<br>
&lt;dael> fantasai: Cascade has an open issue on same-origin check for the quirks mode. After that we should be ready to publish. That should be most of the outstanding edits. Changes list is here^<br>
&lt;dael> fantasai: We made 5 or 6 changes<br>
&lt;dael> astearns: Resolving that one issue will take what?<br>
&lt;dael> fantasai: TabAtkins would know<br>
&lt;dael> TabAtkins: I'd have to review to see if Ana responded<br>
&lt;dael> fantasai: He did<br>
&lt;fantasai> s/Ana/Anne/<br>
&lt;dael> TabAtkins: Is he saying I'm right? If yes it's easy<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/4838#issuecomment-762052244<br>
&lt;dael> fantasai: I don't know. There's the comment ^<br>
&lt;dael> fantasai: Do we want to take a resoltuion to publish once you and Anne decide wording<br>
&lt;dael> astearns: Prop: Publish cascade after resoltuion of 4838<br>
&lt;dael> RESOLVED: Publish cascade after resolution of 4838<br>
&lt;dael> astearns: Anything else on this?<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3827#issuecomment-763824485 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 January 2021 17:54:31 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:38 UTC