Articles on open source software including Drupal, web development, and other specialist topics...
With the overhaul of many API's in Drupal 8, one of the new kids on the block is the configuration system with its integration with the entity API. This means that we can now define configuration entities (that work much like the regular content entities) for the purpose of managing more complex configuration. For example, a View is a configuration entity and so is a field or an image style.
Half a year ago I wrote a blog post about various stumble blocks I had run into in my first year as a Drupal developer. I called them gotchas because they were not necessarily bugs - they might just be Drupal’s way of doing things which may confuse people new to or experienced with Drupal. Sometimes they are annoyances - they could be called paper cuts too. The post got some attention - which was great because people started sending me tips about things they ran into. Now there is time for a new round!
- Nowadays there is decent support for webfonts, so we are using less and less sprites, but if we do, we want to have a solution that responds to high resolution screens. There is a fairly easy solution if we use 1 high res inline image per icon and scale it to fit its container. But this way we'll loose all the benefits that a sprite map gives us. So how can we use sprites for different resolutions? The most common use of a sprite is as a background in a container with a fixed size.
IE8 is resisting to die. Internet Explorer 8 world-wide usage is more popular than IE9 and even IE10