Verify your code does not rely on removed polyfills
Following on from our previous announcement, the accessible autocomplete code is no longer transpiled and polyfilled to support IE8-10.
However, because the polyfills create or extend global objects, you might have other code in your service unintentionally relying on the inclusion of these polyfills. You might need to introduce your own polyfills or rewrite your JavaScript to avoid using the polyfilled features.
Check for minor visual changes in the rendering of the component
We've made some style adjustments to the stylesheet shipped with the component to make its colours, height, line-height and padding match those of the latest version of GOV.UK Frontend's <input>.
If you're using this stylesheet:
check if our style update affects the rendering of the component in your service, and adjust if necessary
if you were adding to the default style's to match GOV.UK Frontend's input,
look for CSS declarations you may now be able to remove
Use the new autocomplete__status class in your CSS (or <CSS_NAMESPACE>__status if you set the cssNamespace option) to customise the styles of the component's status element (hidden element that makes announcements to assistive technologies).
Breaking changes
Verify your code does not rely on removed polyfills
Following on from our previous announcement, the accessible autocomplete code is no longer transpiled and polyfilled to support IE8-10.
However, because the polyfills create or extend global objects, you might have other code in your service unintentionally relying on the inclusion of these polyfills. You might need to introduce your own polyfills or rewrite your JavaScript to avoid using the polyfilled features.
This change was introduced in pull request #612: Update packages, configs + Node.js 20.
Check for minor visual changes in the rendering of the component
We've made some style adjustments to the stylesheet shipped with the component to make its colours, height, line-height and padding match those of the latest version of GOV.UK Frontend's
<input>.If you're using this stylesheet:
This change was introduced in pull request #644: Align CSS styles with GOV.UK Frontend.
New features
Options to add classes to parts of the component
Use these new options to add your own classes to parts of the component:
inputClassesfor theinputelementhintClassesfor the suggestion hint (inputelement appearing when the text typed by the user matches the start of an option)menuClassesfor theulelement listing the optionsYou can also add custom classes to the
ullisting the options through the newmenuAttributesoption, providing aclassNameorclassproperty.This change was introduced in:
inputClassesoption. Thanks to @andreyyudin for contributing this change.New class on the component's status
Use the new
autocomplete__statusclass in your CSS (or<CSS_NAMESPACE>__statusif you set thecssNamespaceoption) to customise the styles of the component's status element (hidden element that makes announcements to assistive technologies).This change was introduced in pull request #620: Add className attribute to status component. Thanks to @lennym for contributing this change.
Fixes
menuAttributesto fix Axe's 'aria-input-field-name' error. Thanks to @mchughbri for contributing this change.