If you two are not in the technical beta, you ought to be. Send Pete LePage an e-mail and I’m sure he’ll agree.

You’re saying that the IE property is msBoxSizing, and that this is undesirable. Your argument is that the property should be MsBoxSizing. Sorry, I didn’t get that at first.

The problem with your patch — of using browser detection to provide a custom camelCase for IE — is that if you inform enough people to do this, it will gain adoption and then internet explorer will not be able to change without breaking existing sites.

This will lead to developers who used this property blaming Microsoft, when it’s really partially the fault of the developer who used such techniques.

Garrett

var toCamelCaseExp = /-([a-z])/, R = window.RegExp;
function toCamelCase(s) {
for(; toCamelCaseExp .test(s); s = s.replace(toCamelCaseExp , R.$1.toUpperCase()));
return s;
}

toCamelCase(”-moz-border-radius”);

MozBorderRadius

view.getComputedStyle(el,”).MozBorderRadiusTopright;

I too am failing to see the reason why browser detection is necessary to convert to camel case.

var toCamelCaseExp = /-([a-z])/, r = window.RegExp;
function toCamelCase(s) {
for(var exp = toCamelCaseExp; exp.test(s); s = s.replace(exp, R.$1.toUpperCase()));
return s;
}

console.log(toCamelCase(”-moz-border-radius”));

I usually don’t find it necessary to do this because it’s possible to just use the camel-cased value from the start.

document.defaultView.getComputedStyle(el, ”).MozBorderRadius;

Shorthand values in Mozilla always return the empty string, so it’s necessary to specify each one individually.

var el = document.getElementById(’accel’),
view = document.defaultView;
view.getComputedStyle(,”).MozBorderRadiusTopright;

Regards,

Garrett