Adds CSS state for Chrome 125

[rachelandrew]

Chrome is shipping the updated syntax, the old dashed ident syntax will be deprecated.

https://chromestatus.com/feature/5586433790443520

Is leaving the note the right thing to do here?

[hamishwillee]

@Elchi3 @queengooborg In the original spec you'd set a custom state by adding a dashed ident like --my-ident to a CustomStateSet, and then you'd match against that identifier in CSS using the ident: :--my-ident. The spec now says you don't need to use a dashed ident (though you can use whatever identifier you like with the new selector), and you match using the :state() selector function.

This update is good. My question is whether we need to somehow add a separate feature to indicate the dashed ident format, because this is still supported by current chrome, and we might want to show the deprecation path? No idea how you do that. Would be nice to avoid if we can using the note.

[hamishwillee]

So not sure if this is "sufficient" as a note, and even if this is sufficient, it slightly implies that the dashed ident form is no longer allowed. I'm not messing with it because the BCD team know better than me.

[Elchi3]

Thanks @hamishwillee, I think you are proposing the following?
Do you want to make that change, @rachelandrew?

"chrome": [
  {
    "version_added": "125"
  },
  {
    "version_added": "90",
    "notes": "Supported using a dashed-ident (such as <code>:--foo</code>) instead of <code>:state()</code>."
  }
]

[Elchi3]

If the deprecated syntax will ever get removed, we could then have:

"chrome": [
  {
    "version_added": "125"
  },
  {
    "version_added": "90",
    "version_removed: "200",
    "notes": "Supported using a dashed-ident (such as <code>:--foo</code>) instead of <code>:state()</code>."
  }
]