[css-text-4] Is hyphenate-character stable enough to ship?

[jfkthame]

I'm interested in implementing the hyphenate-character property in Gecko.

Checking other browsers, I see that both Webkit and Blink have this property, but with the prefixed name -webkit-hyphenate-character; the non-prefixed version does not appear to be supported.

So... should we consider hyphenate-character stable enough that it's OK to implement and ship as an unprefixed property (and create some corresponding web-platform-tests), or would this be premature?

I see there has been some discussion (e.g. #2975) of additional potential values, e.g. to support cases where hyphenation inserts a character after the line-break in addition to (or instead of) before the break. But I don't think this needs to block shipping of the simple property as currently spec'd; a future extension could still introduce a two-valued syntax, for example, without affecting the current single-valued syntax.

[drott]

CC @kojiishi

[css-meeting-bot]

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

The full IRC log of that discussion

<TabAtkins> Topic: can we ship hyphenate-character?
<TabAtkins> jfkthame: Question in the title
<TabAtkins> jfkthame: webkit and blink have this, but -webkit- prefixed
<TabAtkins> astearns: And Firefox has this unprefixed?
<TabAtkins> jfkthame: Yes, behind a nightly flag
<TabAtkins> jfkthame: So quesiton is whether we can ship it unflagged
<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
<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
<TabAtkins> astearns: What's state of the spec?
<TabAtkins> florian: WD, this is level 4
<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
<TabAtkins> astearns: objections?
<TabAtkins> RESOLVED: hyphenate-character is shippable; we'll add it to the Snapshot 2022 list of exceptions
<TabAtkins> fantasai: Do we want to resolve to publish a Draft Note 2022 with this change?
<TabAtkins> astearns: I think we should publish as needed, yes.
<TabAtkins> chris: Seems much better to publish as we ahve updates, yes
<TabAtkins> astearns: So proposed reoslution is we publish a Draft Note for 2022
<fantasai> (Now that we have a Draft Note)
<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?
<TabAtkins> fantasai: I didn't like this; I think it's useful to have snapshots on a yearly basis
<TabAtkins> fantasai: Just walking back thru publish history isn't the same
<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
<TabAtkins> fantasai: I think your point is valid but it is true for all leveled/versioned things
<TabAtkins> fantasai: That's an issue for the templates
<TabAtkins> astearns: So no reoslution, we'll break