Custom elements are small UI components that you can re-use all over your application, while at the same time keeping you markup tidy and semantic. However, in practice, you often cannot fit the same element everywhere. Imagine the autocomplete built in the previous blog post. If you place the autocomplete in a small sidebar, you need the results appearing in a pop-over list. However, if you want to build a real search page, you want the results always visible in a clear, big area. The solution to this is a new concept, named Responsive x-tags.
After some delay (won’t get into that now) I get to write something new. After spending 2 days in the 2013 Fronteers Conference, I finally got the time and energy to write something about the hottest part of Web Components: custom elements. Read More…
While working on the Launchpad Portal, we needed to detect when some elements had their size changed (user had the option to change their width or height). However there is not native resize event triggered so we had to come up with another solution.
Searching around a bit, the most common way for something like this, would be setting a timeout and every few milliseconds check is the values have changed or if they are the save. However, as an experiment I came up with a more elegant way.