getComputedStyle in IE

From: CHYRON (DSMITHHFX)17 Jan 2013 18:33
To: ALL3 of 6
I was getting all hung up on elaborate jquery syntax structures when the answer turned out to be dead simple. 2.5-hours later (drum roll)...

---
function contentpadding()   {
   var contentw = $("#content").css("width");
   var containerw = $("#container").css("width");
   var contentpadding = (parseInt(containerw) - parseInt(contentw)) / 2;
   if (parseInt(containerw) > 1040)   {
      document.getElementById("content").style.paddingLeft = contentpadding + 'px';
      document.getElementById("content").style.paddingRight = contentpadding + 'px';
   } else {
      document.getElementById("content").style.width = (contentw - 72) + 'px';      
   }
}
---
From: af (CAER)17 Jan 2013 23:16
To: CHYRON (DSMITHHFX) 4 of 6
Do you know about box-sizing: border-box; ? I didn't read your code all that carefully but I have a feeling that might come in handy.

Oh and you should always specify the base parameter for parseInt() otherwise you'll get unexpected values if the strings you're parsing have leading zeroes.
EDITED: 17 Jan 2013 23:18 by CAER
From: CHYRON (DSMITHHFX)18 Jan 2013 01:48
To: af (CAER) 5 of 6
I wasn't aware of it (border-box). It looks like it could be very useful. Haven't had any problems with parseInt in my very limited use of it.
From: af (CAER)18 Jan 2013 10:16
To: CHYRON (DSMITHHFX) 6 of 6
it was just a heads-up really – if you do
code:
parseInt("0034")
for example, you'll get 28 as a result, whereas if you do
code:
parseInt("0089")
you'll get either 0 or NaN.

In browsers which support ECMAScript 5, which is basically just Chrome at the moment,  this silly behaviour is removed and parseInt works how you'd expect. Still, best to be on the safe side.
EDITED: 18 Jan 2013 10:19 by CAER