A lot's been happening this week as people get things ready for Christmas.
Quick note about HTML5 Form validity and browser differences
Is your Fullscreen API code up to date? Find out how to make it work the same in modern browsers
jQuery .data() considered potentially harmful
You're Doing Node.js Wrong! Avoid Synchronous Code
Retrieving Property Names with Object.getOwnPropertyNames and Object.keys
Intro to Shadow DOM
Building a Box That Sticks While You Scroll
Bigfoot - A jQuery plugin for empowering footnotes
Switchery - iOS 7 style switches for your checkboxes
50 Most Useful jQuery Plugins from 2013
[A fresh & lightweight HTML5 game engine - and a [url="http://melonjs.github.io/tutorial/"]melonJS tutorial](https://github.com/melonjs/melonJS)
How to build a game with Three.js
The Value of Testing
How to Unit Test Controllers In AngularJS Without Setting Your Hair On Fire
What have you learned the most about from this weeks articles?
Please PM us if you have anything of interest for the next issue, and happy reading! - [Paul & [URL="http://www.sitepoint.com/forums/private.php?do=newpm&u=184222"]Pullo](http://www.sitepoint.com/forums/private.php?do=newpm&u=158377)
I commented on the original article as well, it's more about a slightly wrong approach. It should perform the :invalid query in the current form. Think multiple forms on the page. And the browser difference is documented FireFox behavior: https://developer.mozilla.org/en-US/docs/Web/CSS/:invalid#Browser_compatibility
This topic is now closed. New replies are no longer allowed.