Vaadin 22 post mortem
Обзор измений в релизе Vaadin web components v22.0.0.
Today is the release day! Meet Vaadin web components 22.0, a new major release with a bunch of accessibility fixes that my team has been working on since July. As usual, it's time for me to share a short post mortem.https://t.co/TU0ZjduPLE
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
In order to fix some accessibility issues, we had to do many breaking changes to the DOM structure and styling API of our field components. Check out the Upgrading Guide if you are using an older version.https://t.co/E2nw8DtYEx
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Personally, I'm especially proud of all the work we have done to make vaadin-combo-box accessible. Both the input field and dropdown items are now placed in light DOM to make ARIA ID references work.https://t.co/aAlX0lYVlZ
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
All of our input field web components (text-field, combo-box, date-picker etc) now share the same logic for handling slotted input and label elements. The implementation is inspired by Lion web components.https://t.co/toJX8vF1Xh
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
We also updated a few smaller web components like button, checkbox, radio-button and radio-group, to address the a11y issues that were reported long ago. Huge thanks to @vursen for working on those.
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
There are other notable changes in Vaadin 22 that are not related to a11y. For example, we removed the previously deprecated render() method to make future web components migration to Lit easier.https://t.co/bqhBCopiFV
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Another important thing: we have updated the npm package names to not repeat "vaadin" twice so you can write cleaner imports. The old packages are preserved for backwards compatibility in this release.https://t.co/KiXIeVXyOo
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Related to the above: we updated the custom element classes to remove the redundant "Element" suffix. So, when using TypeScript, you can import Grid and not GridElement. It makes the code a bit more readable.https://t.co/xBeaxfUsUp
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
There is a lot more in Vaadin 22 than what I've shared so far. And I'm so excited about every single feature! But the best thing is that the team has already started to work on Vaadin 23 (first alpha release is out).https://t.co/PnNGjlXYjK
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Among other improvements, we are going to continue working on accessibility fixes in Vaadin 23. Check out the GitHub project board for the list of fixes shipped in Vaadin 22 and those planned for the next major.https://t.co/2MOtzwZ2lX
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Also, we keep working on gradually getting rid of some Polymer legacy. One small step is creating a local copy of the gestures module that can be later replaced with native events, or possibly reactive controllers.https://t.co/bEtsUrO45z
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Finally, one more change coming to Vaadin 23 (merged to master but not released yet) is LitElement support for vaadin-themable-mixin. This gets us even closer to upgrading some web components to Lit in the future.https://t.co/7Edsglxznm
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Overall the work that the Vaadin design system has been doing this year is so impressive that I can't resist sharing it publicly every time we release a new major version. Thanks to my team and everyone involved!
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Also, I would like to use this occasion to say special thank you to @Knoobielein for the invaluable help with testing, feedback, and guidance with the accessibility work. It really means a lot to our team.https://t.co/HbLWxufeA5
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021
Stay tuned to learn more about Vaadin web components 23.0 when the time comes (and hopefully more good news about us moving to Lit). And of course, any feedback about the new release is highly appreciated.
— Serhii Kulykov 🇺🇦 (@serhiikulykov) December 1, 2021