fernandes.io

Today, I stumbled across something strange in IE8 where it was able to identify and render HTML5 elements like <section> and <article> without the use of the HTML5-shiv or even without having to use document.createElement() . I figured it had to do with an "xmlns" attributed which accidently landed up on one of the <section> tags in my html. To illustrate my point, I'll use variations of the following HTML: <!DOCTYPE html> <html>   <head>     <style>       .outer,.middle,.inner {         padding: 20px;       }       .outer {         border: 1px solid black;         background: lightblue;       }       .middle {         border: 1px solid red;         background: yellow;       }       .inner {         border...

The maven-karma-plugin allows running your jasmine tests via karma from maven. For the most part, the documentation given in the readme.md at  https://github.com/karma-runner/maven-karma-plugin  is sufficient if you just want to run unit tests using karma. However, if you want to use the karma to run your unit tests as well as your e2e tests, you need to specify it in your pom.xml in a slightly different way. Firstly, the <configuration /> goes inside an <execution /> . Then every <execution /> needs to have an <id /> which should be unique. <plugin>     <groupId>com.kelveden</groupId>     <artifactId>maven-karma-plugin</artifactId>     <version>1.1</version>     <executions>         <execution>             <id>unit</id>             <goals>       ...

A very short note on something I came across today (I might elaborate on this later..) In a dot Net application, I found that when I tried to use the jQuery UI Autocomplete plugin, there was a conflict. The errors and messages that I came across in the console of Chrome, indicated that there was an API mismatch in the jQuery UI library and the jQuery UI Autocomplete plugin. After a bit of inspection, I found out that dot Net had it's own version of jQuery UI, which actually was a concatenation of many jQuery UI plugins along with the jQuery UI core (even though it was named as jquery-ui.js!). It was pretty straightforward to fix this - I just had to get rid of one of them, either the dot Net's version or the original jQuery UI's version. In my case, since it was a dot Net application, I thought it might be better to retain Microsoft's copy of  jQuery UI!