- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jan 2022 16:56:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `can we ship hyphenate-character?`, and agreed to the following: * `RESOLVED: hyphenate-character is shippable; we'll add it to the Snapshot 2022 list of exceptions` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: can we ship hyphenate-character?<br> <TabAtkins> jfkthame: Question in the title<br> <TabAtkins> jfkthame: webkit and blink have this, but -webkit- prefixed<br> <TabAtkins> astearns: And Firefox has this unprefixed?<br> <TabAtkins> jfkthame: Yes, behind a nightly flag<br> <TabAtkins> jfkthame: So quesiton is whether we can ship it unflagged<br> <TabAtkins> fantasai: I think so. I don't remember there being any issues against this particular property for the many years it's been around<br> <TabAtkins> florian: Agree. You noted there might need to be extensions later to be smart about some details, but they can be put on top of the current value set<br> <TabAtkins> astearns: What's state of the spec?<br> <TabAtkins> florian: WD, this is level 4<br> <TabAtkins> astearns: So we resolve this is okay to publish, and add this to the snapshot list of things that are shippable ahead of process<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: hyphenate-character is shippable; we'll add it to the Snapshot 2022 list of exceptions<br> <TabAtkins> fantasai: Do we want to resolve to publish a Draft Note 2022 with this change?<br> <TabAtkins> astearns: I think we should publish as needed, yes.<br> <TabAtkins> chris: Seems much better to publish as we ahve updates, yes<br> <TabAtkins> astearns: So proposed reoslution is we publish a Draft Note for 2022<br> <fantasai> (Now that we have a Draft Note)<br> <TabAtkins> chris: since /TR/CSS goes to the snapshot, why don't we publish a NOte series with "css" as the shortname, so every time it's not the first draft, but just an update?<br> <TabAtkins> fantasai: I didn't like this; I think it's useful to have snapshots on a yearly basis<br> <TabAtkins> fantasai: Just walking back thru publish history isn't the same<br> <TabAtkins> chris: If you follow history right now, it'll say "css 2022 has been published once", and you can't go back to 2021 from there<br> <TabAtkins> fantasai: I think your point is valid but it is true for all leveled/versioned things<br> <TabAtkins> fantasai: That's an issue for the templates<br> <TabAtkins> astearns: So no reoslution, we'll break<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6887#issuecomment-1016667299 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 January 2022 16:56:20 UTC