Andy Mantell

I've managed to work around the bug for the moment by using a `` after the legend instead of using a bottom margin to achieve the visual spacing I need....

Am experiencing the same here in Chrome 47.0.2526.80 on Windows. On first load with an empty cache it reports true. All subsequent loads with a primed cache report false.

Just to add some more information on this - this bug is rearing it's head when attempting to use the accessible-autocomplete under the new govuk design system, which happens to...

Yes sorry it is not the same issue. I got fixated on the fact that the solution would be the same for both problems. I'll raise a new ticket...

I've made a demo here: https://accessible-autocomplete-govuk-design-system.glitch.me/

@Fenwick17 Agreed. It's on my radar - will put some in when I next get a moment.

@sarawilcox No the breaking change got released already. The ErrorSummary is working as expected and not exhibiting this bug in the _released_ version of nhsuk-frontend. The outstanding piece of work...

An interesting, related point of difference [compared to govuk-frontend](https://github.com/alphagov/govuk-frontend/tree/main/src/govuk/components/skip-link) is that we place focus on the first h1 in the page whereas govuk-frontend places focus on the main wrapper. They...

I don't mind too much either way, so I'd be happy enough for these to be unquoted personally. I see govuk did it here, and consistency with them is good:...

Have left a similar post over on https://github.com/nhsuk/nhsuk-service-manual-community-backlog/issues/7#issuecomment-1592862857 but to summarise it: On 111 online we prefer full width buttons: - For consistency with nhs login and our old codebase...