This repository has been archived by the owner on Oct 16, 2024. It is now read-only.
Update dependency accessible-autocomplete to v3 #778
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.0.4
->^3.0.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
alphagov/accessible-autocomplete (accessible-autocomplete)
v3.0.1
Compare Source
Fixes
aria-controls
to aria propsaria-labelledby
into computed menu propsv3.0.0
Compare Source
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:
look for CSS declarations you may now be able to remove
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:
inputClasses
for theinput
elementhintClasses
for the suggestion hint (input
element appearing when the text typed by the user matches the start of an option)menuClasses
for theul
element listing the optionsYou can also add custom classes to the
ul
listing the options through the newmenuAttributes
option, providing aclassName
orclass
property.This change was introduced in:
inputClasses
option. Thanks to @andreyyudin for contributing this change.New class on the component's status
Use the new
autocomplete__status
class in your CSS (or<CSS_NAMESPACE>__status
if you set thecssNamespace
option) 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
menuAttributes
to fix Axe's 'aria-input-field-name' error. Thanks to @mchughbri for contributing this change.Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone Europe/London, Automerge - "after 10am every weekday,before 4pm every weekday" in timezone Europe/London.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.