[css-counter-styles] Mark <image> in <symbol> at risk?

[upsuper]

I didn't implement that in Gecko, and I'm not motivated to do so anytime soonish. Also it doesn't seem there is impl interest from other vendor yet. Having some feature which is not implemented and not going to be implemented in any browser in foreseeable future in a CR is probably not a good idea?

Also, given that some of the usecases of <image> are now covered by emoji, I guess <image> as <symbol> isn't that important now?

[tabatkins]

Yeah, sounds reasonable (and avoids some complexities caused by counter() no longer being a <string>).

[tabatkins]

(I've gone ahead and marked it as at-risk, but want a WG heads-up on Wednesday.)

[css-meeting-bot]

The Working Group just discussed [css-counter-styles] Mark <image> in <symbol> at risk?, and agreed to the following resolutions:

• RESOLVED: Mark <image> in <symbol> at risk

The full IRC log of that discussion

<dael> Topic: [css-counter-styles] Mark <image> in <symbol> at risk?
<dael> github: https://github.com//issues/1991
<dael> TabAtkins: xidorn pointed out the image value no one has impl and he's not interested in impl. I noted it complecates the definintion of counter in unexplained ways. I'm happy to mark as at risk on track to drop.
<dael> astearns: Any objections to Mark <image> in <symbol> at risk
<fantasai> https://github.com/w3c/transitions/issues/23
<dael> RESOLVED: Mark <image> in <symbol> at risk
<dael> fantasai: We just submitted it as a transition.