Update for Safari 17.4 beta (19618.1.15)

[Elchi3]

The Open Web Docs BCD collector v10.8 found new features shipping in Safari 17.4 beta (19618.1.15) which was released yesterday. Currently, the collector covers about 88% of BCD, so the following list might not be exhaustive. Also, if a feature is in Safari TP and/or behind flags, it is not considered here.

I ran the collector previously for Safari 17.4 beta (19618.1.11.11.3). Here's the PR: #22101. This PR is about 19618.1.15 and new features from the previous beta release were found:

• api.CustomStateSet
• api.CustomStateSet.add
• api.CustomStateSet.clear
• api.CustomStateSet.delete
• api.CustomStateSet.entries
• api.CustomStateSet.forEach
• api.CustomStateSet.has
• api.CustomStateSet.keys
• api.CustomStateSet.size
• api.CustomStateSet.values
• api.CustomStateSet.@@iterator
• api.Element.ariaDescription
• api.Element.attachShadow.init_clonable_parameter
• api.Element.checkVisibility
• api.ElementInternals.states
• api.ShadowRoot.clonable
• css.selectors.state

https://developer.apple.com/documentation/safari-release-notes/safari-17_4-release-notes confirms these features.

Full list of features that BCD considers shipping in Safari 17.4 (taking into account the previous PR)

• api.AbortSignal.any_static
• api.CSSScopeRule
• api.CSSScopeRule.end
• api.CSSScopeRule.start
• api.CustomStateSet
• api.CustomStateSet.add
• api.CustomStateSet.clear
• api.CustomStateSet.delete
• api.CustomStateSet.entries
• api.CustomStateSet.forEach
• api.CustomStateSet.has
• api.CustomStateSet.keys
• api.CustomStateSet.size
• api.CustomStateSet.values
• api.CustomStateSet.@@iterator
• api.DOMMatrixReadOnly.scaleNonUniform
• api.Document.parseHTMLUnsafe_static
• api.Element.ariaDescription
• api.Element.attachShadow.init_clonable_parameter
• api.Element.checkVisibility
• api.Element.setHTMLUnsafe
• api.ElementInternals.states
• api.HTMLInputElement.showPicker.date_input
• api.HTMLInputElement.showPicker.datetime_local_input
• api.PublicKeyCredential.getClientCapabilities_static
• api.SVGFESpecularLightingElement.kernelUnitLengthX
• api.SVGFESpecularLightingElement.kernelUnitLengthY
• api.SVGRenderingIntent (removal)
• api.ShadowRoot.clonable
• api.ShadowRoot.setHTMLUnsafe
• css.at-rules.scope
• css.properties.content.alt_text
• css.properties.text-decoration-thickness.percentage
• css.properties.text-wrap-mode
• css.properties.text-wrap-mode.nowrap
• css.properties.text-wrap-mode.wrap
• css.properties.text-wrap
• css.properties.text-wrap.nowrap
• css.properties.text-wrap.wrap
• css.properties.transition-behavior
• css.properties.white-space-collapse
• css.selectors.grammar-error
• css.selectors.spelling-error
• css.selectors.state
• javascript.builtins.ArrayBuffer.detached
• javascript.builtins.ArrayBuffer.transfer
• javascript.builtins.ArrayBuffer.transferToFixedLength
• javascript.builtins.Map.groupBy
• javascript.builtins.Map.groupBy
• javascript.builtins.Object.groupBy
• javascript.builtins.Object.groupBy
• javascript.builtins.Promise.withResolvers
• svg.elements.feSpecularLighting.kernelUnitLength
• webassembly.extended-constant-expressions

cc @jdatapple

[queengooborg]

Should this be the same compat history as Element.clonable?

[Elchi3]

I think in Element.json the situation is slightly different. The cloneable name shipped in 16.4 already whereas here it was never shipped outside of preview. So I would leave this as is.