Todays Wacky bug of the Day is not IE8-specific. Today's Wacky Bug is brought to us by Chrome and Firefox. I haven't tried IE11 yet but Chrome throws an error when var i = 0; That is standard code for setting a variable (i) to equal zero. All Chrome will tell me in the console is 'Uncaught SyntaxError: Unexpected token ILLEGAL'. Firefox was a little more informative by returning '†< var i = 0;'. So I am getting some funky character before my variable is being set. Strip everything out before the var call and the mystery character that doesn't show up when looking at the code is still showing in the console. Delete everything before the 'i' and it finally disappeared. This is why it takes so long to program. Stupid browsers.
Wacky IE8 Bug of the Week: I added a tooltip to an information icon today at work where mousing over the information icon displays an overlay with possible options for a form field. Everything looked good in Chrome, Firefox, IE 9/10/11. IE8 not so much. IE8 would load an external javascript related to some other module on the page and while it was loading, the hover worked. As soon as it timed out on trying to do whatever it was trying to do, the hover effect stopped working. This is on local. On the test server, it did what it had to with the external javascript right away so the hover effect never worked. In the course of troubleshooting with jHarmies, I figured out that changing the information icon color keeps the hover effect working consistently. I set the color to be unnoticable and checked it into the test environment. QA approved.Not sure what was causing it but we won't be supporting IE8 in the coming months so I wasn't going to waste to much time trying to figure out what IE8s problem was.