remove dom2property from css whitelist

The css whitelist has an element 'dom2property' that's intended to
map a css name like 'margin-left' to a dom name like 'marginLeft'.

I'm eliminating it, because:

1. It's unnecessary. The name conversion is regular except for
float->cssFloat, and it's unlikely that any other css properties
will be irregular.

2. It's a maintenance hazard. Specifying an incorrect dom2property
will cause mysterious failures. And failing to specify a correct
dom2property may also cause mysterious failures.

There was also legacy support for style->styleFloat instead of cssFloat,
which is for IE<=8, which we're not supporting, so I'm removing the
styleFloat code.

[felix8a, 2013-08-22 20:40:49]

+kpreid since mikesamuel is on vacation. feel free to ignore, this isn't urgent

[kpreid2, 2013-08-22 20:55:26]

LGTM

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/lang/css/c...
File src/com/google/caja/lang/css/css3-defs.json (right):

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/lang/css/c...
src/com/google/caja/lang/css/css3-defs.json:5: "This differs from the spec in
that it has ranges on some numeric values.",
long line

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
File src/com/google/caja/plugin/domado.js (right):

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:1076: // TODO(kpreid): Review whether this
has unnecessary features (as we're
I believe the answer to this question is "no", and you can delete this comment.

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:1087: if (cssName === 'float') { domName =
'cssFloat'; }
I'd reorder/combine the above two statements because the computed domName is
immediately discarded.

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:1093: isDomName: function (p) {
Thanks for less confusing names.

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:1099: dom2css: function (p) {
I'd prefer domToCss or maybe even domToCssName.

[felix8a, 2013-08-22 21:40:05]

The css whitelist has an element 'dom2property' that's intended to
map a css name like 'margin-left' to a dom name like 'marginLeft'.

I'm eliminating it, because:

1. It's unnecessary. The name conversion is regular except for
float->cssFloat, and it's unlikely that any other css properties
will be irregular.

2. It's a maintenance hazard. Specifying an incorrect dom2property
will cause mysterious failures. And failing to specify a correct
dom2property may also cause mysterious failures.

There was also legacy support for style->styleFloat instead of cssFloat,
which is for IE<=8, which we're not supporting, so I'm removing the
styleFloat code.

[felix8a, 2013-08-22 21:40:23]

updated snapshot

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/lang/css/c...
File src/com/google/caja/lang/css/css3-defs.json (right):

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/lang/css/c...
src/com/google/caja/lang/css/css3-defs.json:5: "This differs from the spec in
that it has ranges on some numeric values.",
On 2013/08/22 20:55:27, kpreid2 wrote:
> long line

Done.

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
File src/com/google/caja/plugin/domado.js (right):

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:1076: // TODO(kpreid): Review whether this
has unnecessary features (as we're
On 2013/08/22 20:55:27, kpreid2 wrote:
> I believe the answer to this question is "no", and you can delete this
comment.

Done.

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:1087: if (cssName === 'float') { domName =
'cssFloat'; }
On 2013/08/22 20:55:27, kpreid2 wrote:
> I'd reorder/combine the above two statements because the computed domName is
> immediately discarded.

Done.

https://codereview.appspot.com/13060045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:1099: dom2css: function (p) {
On 2013/08/22 20:55:27, kpreid2 wrote:
> I'd prefer domToCss or maybe even domToCssName.

Done.

[kpreid2, 2013-08-22 21:46:58]

LGTM

[felix8a, 2013-08-22 23:58:17]

@r5573