We're excited to reveal the winners of the 2023 Vaadin Collaboration Kit Challenge! 🎉
Thank you to everyone who participated and took the time to design and build incredible collaborative web apps! See the winners: https://t.co/MTgVJ7htdR
Less than a week (but a full weekend!) left to design or code something for https://t.co/CIS6lxQCEs to win prices!
I did this (we Vaadiners can't participate in the official challenge): https://t.co/eedwHF8uhJ Still some room for improvement... 😉😉
@marcushellberg@artursignell@vaadin Customize how? If we allow free style customization per individual component instances, I feel that’ll be a sure way to get inconsistencies in your app. But per-component type, that’s something I agree (i.e. customize all primary buttons).
@jh3yy Oh, thanks, I hadn’t noticed that article yet! Now I’m really looking forward to the [popup] attribute :) Any news regarding browser support, is any other browser working on it?
Hey, @jh3yy, I really liked your article about the top layer: https://t.co/gr9zSfyjYz
But I wish you would have mentioned the limitation of <dialog>.show() more prominently, that it won't be shown in the top layer, and is just a regular position:absolute element.
@mars3142@vaadin@penpotapp Thanks for the suggestion, I wasn't aware of Penpot! I don't think we have the resources to create a library for it that at the moment, but I will keep it in mind.
I think Figma is still a just as good as before. Is pricing the main reason you want to use Penpot instead?
Coming soon to the #vaadin docs site: an icon set generator! Preview available for testing here: https://t.co/O8WRg6PDbU
Let me know if you find it useful and/or if your problems using it 🙏
@jh3yy@tomayac @hdv If only there was a “popup” primitive in HTML that allowed placing things on the top layer. I would assume a non-modal <dialog> to be that, but unfortunately it’s just a <div style="position: absolute"> from a layout/rendering perspective.
Hey #CSS devs!
Why do you use `:root` instead of `html` for defining custom properties?
To me, it seems like unnecessary specificity (pseudo-class vs element).
📆Save the date!
Accessibility standards are on the rise. Join our upcoming webinar: Accessibility Standards and Legislation on May 19th, to learn more about digital accessibility, assistive technologies, and upcoming accessibility legislation. Sign up: https://t.co/qDuXDBDtId
@Knoobielein@RolfSmeds Speaking of the router, I understood that the new Navigation API could be something that could replace it or at least significantly help with the implementation. Looking forward to that as well, although I’m feel more and more like an MPA (vs SPA) advocate recently.
@joonaslehtinen@RolfSmeds@Knoobielein@vaadin Thanks! That was the one video I explicitly watched from all the things that Google presented last week.
Transitions have their time and place. I need to start thinking what and where would make sense in the types of apps we target. Don't want to add superfluous friction.
“Contemporary man attempts to create the world in his image, to build a totally man-made environment, and then discovers that he can do so only on the condition of constantly remaking himself to fit it.” — Ivan Illich