UIkit 3.14 – Updated Drop, Sticky and Navbar
Today we are happy to introduce UIkit 3.14. With this update we continue to modernize our JavaScript components. We started with the Parallax component, and this time we focused on the Drop component and further refinements for the Sticky and Navbar components. Let's take a look.
Make sure to subscribe to our YouTube channel and join our Discord Chat Server for all news and discussions.
Drop Component
UIkit 3.14 heavily improves the Drop component, in particular its responsive behavior. Before, when a dropdown did not fit the viewport, it automatically flipped its position to stay in view. This often did not fit on smaller viewports and created a scrollbar. This is why we introduce a new shifting behavior. Now instead of flipping, the element will shift its position in order to better fit in view. And if it gets too large for the viewport, it will start shrinking.
If the element the dropdown is aligned to is in the way of the shifting direction, it will flip to the other side instead. If this is also not possible, the element will flip the axis.
Sticky Component
Our last UIkit 3.12 release already came with a lot of improvements for the Sticky component, but we have refined it even further. First of all, we renamed the top
and bottom
options to start
and end
to bring it in line with the Parallax component. By default, the element becomes sticky when its top border reaches the top of the viewport, and it stays sticky till it reaches the end of the page. With the start
and end
options you can apply an offset to when the element becomes or stops being sticky. Values can be set in any dimension units, namely vw
, vh
, %
and px
. The %
unit relates to the element's height. Both options allow basic mathematics operands, +
and -
.
There is a new overflow-flip
option that disables the sticky behavior for oversized content. If the element is larger than the viewport, the sticky position is flipped, and changing the scroll direction will not affect its position. Together with the start
and end
options you can achieve two nice sticky effects. You can cover an element by following content or reveal it by previous content.
Finally, we completely renewed our documentation and updated UIkit tests.
Navbar Component
Next we have some smaller improvements for the Navbar component. You can justify the navbar items by equally distributing the space between them.
Additionally, Nav, Dropdown and Navbar components can all have subtitles.
And we removed the dropbar push mode from the Navbar component as it felt outdated.
Parallax Component
When working with the Parallax component, we noticed that the usage of the scale property was quite limited. In CSS, it is only possible to set a number or percentage representing the scaling vector. To give you more control, we added support for the vw
, vh
and px
dimension units. Now you can scale an element to a specific pixel value or even relative to the viewport without knowing the element's size.
Migration to UIkit 3.14
There is a small breaking change for the Sticky component, so please take a look at the migration guide. Additionally, we removed support for the Edge Legacy and its EdgeHTML engine, the deprecated Gif component and Safari fallback for focus-visible
. Of course, UIkit 3.14 comes with tons of smaller improvements and fixes. For example, UIkit now loads much faster and is less heavy on the CPU for large pages with many HTML elements. For the full list of features and fixes, check out the changelog.
What's Next
We are glad that the Parallax, Sticky and Drop components are now completely overhauled and modernized. As always, we are looking for your feedback, so let us know what you think about this release in the comments below.
akcreation
hubert.cole
moloseb
roger.walker.arnott
akcreation
jose.a.suarez
sven.mediafish
hanna
sven.mediafish
Are you talking about the message that you postpone the next YoothemePro Beta release.. ;-)
hanna
ozelot
akcreation
Please can we have some communication as to what is happening with Yootheme Pro 2.8? It's gone from expected Q1 (with 'Mega Menus are almost ready' on 24th March), to 'having a beta ready next week' on 26th April, to 'We are postponing the beta' 2 weeks later - and now silence for over 2 weeks.
I more than understand that delays and problems occur, I'm absolutely fine with that, but please at least communicate with us what is going on. Is the beta release now months away again, or is it weeks, days.... what?
Or another suggestion, if Mega Menus were basicallty ready in March (as per your tweet on 24th March), but then you added lots of extra features to 2.8 (as per your tweet on 26th April), why not just release 2.8 with Mega Menus and then put the other features as 2.9?
It's been 6 months since the last Yootheme Pro release, and 6 years waiting for Mega Menu's.
And now, silence again.... please guys - tell us what is happening so we can at least manage our expectations. Even if you say we now have to wait months again, that is better than not telling us anything.
Many thanks in advance,
Keith
hanna
akcreation
Thank you for the update - that sounds promising :)
roger.walker.arnott.63
roberto.coria.2
(I don't even want to know how many page views come from us waiting for an update every day. If this site had ads they could hire one more programmer).
tuunbaq
hanna
akcreation
tuunbaq
sascha
softforge
Lots have tested and added comments to the issues link, but the only comment about the issues is "Confirmed Issues
No issues yet."
Do you want more tests if so can you say what issues have been fixed so people don't keep reporting what you have already cleared.
Is there a Beta 2 coming so that you want people to hold fire and test again?
smint
sven.mediafish
NOTIZ
florianwachter
hanna
softforge
The largest gap in blog posts for a long time and the twitter threads are all about 3rd party extensions recently.
So it's all very quiet on the yootheme front
Things happen, we all know that, but keeping customers informed when things go wrong is an important part of the customer relationship and managing expectations.
It also helps developers who use your products plan and manage their own customers.
I had to start a delayed project with a competitor's template because I know they are active and that the megamenu works with them. If I knew it was going to be a few more weeks I could communicate this to the client and we could rearrange, but the silence means planning is not possible and requests elsewhere for updates have gone unheard. Please yootheme, for your own sake do communicate whats happening, good or bad so we can at least plan and work around the issues.
hanna
The beta of YOOtheme Pro 3.0 was released three weeks ago. It comes with tons of new features which you can test and discuss here https://yootheme.com/support/question/152392
We are still working on Beta 2 to make it feature-complete. There is even one more UIkit feature release coming soon.
Besides that we are reworking all YOOtheme Pro theme packages to make use of the upcoming YOOtheme Pro 3.0 features. This is really a huge workload. The same goes for the new theme packages which we are now optimizing to showcase all the new features.
There is not much to communicate other than that we are working hard to make YOOtheme Pro 3.0 stable. But it is still weeks away.
softforge
Interesting to hear you are reworking all the packages, again it's good to understand just how large this update is.
Thank you for sharing.
resonance
https://yootheme.com/support/question/151022?order=newest
Please feel free to delete this comment after addressing the issue. We're just trying to avoid falling through the cracks again.
NOTIZ
florianwachter
I know you guys for years - you were that reliable in dates and always in time. What happened to you the last years?
I really have no idea, but isn´t it possible to engage a guy, just to create a template every month. You could win so much confidence and trust with regular posts. . .
You have such a great Company and such a great Community-Feedback. Don´t waste that.
"Meantime: 26 days after the - "next week" - promise. . . by the way
and the betas are great - yes. But we can´t sell them as they are what they are -- Betas. . .