Fix problems with the NPM build
We fixed the issue by explicitly adding the required Babel plugin to our Babel configuration, and we decided to use a static browserlist to prevent similar problems in the future. I want to thank @scasei for reporting this issue and contributing a pull request to fix it.
Thanks to our partner datenwerk, we were able to fix an accessibility issue with the sulu-link tag. Previously, the sulu-link tag automatically added the page title as fallback for the
title attribute of a rendered link. This impacted accessibility because
title attributes were being read out twice by screen readers if the content of the link matched the
title attribute. We decided to remove this fallback - the sulu-link tag no longer automatically sets a
Read more about working with the
title attribute in this post from 24 Accessibility.
What is coming next?
We have already planned a new feature for Sulu 2.6 - the next minor release of Sulu - which I think you will like a lot. More information about this will be published in an upcoming blog post.
As always, we are happy to hear your feedback about newly released features and bug fixes. Feel free to create an issue or a discussion on GitHub for bugs and feature requests. You can also contact us via Slack or our website anytime.