Created attachment 596028 [details] [diff] [review]
Currently, we call ParseSpecialIntValue ("rules for parsing dimension values" in the spec), and then pull out the percentage's value, and multiply it by 100 (for cellspacing only in quirks mode) to get the result we would already have got if we parsed the value as a simple integer.
It seems to make much more sense to just parse the value as the spec requires and remove all this hackery.
Comment on attachment 596028 [details] [diff] [review]
In what way does this affect developers? I don't think it does.
This made us interpret cellspacing=10% as 10 pixels outside quirks mode (was ignored previously). There may be something on the quirks mode page to update?
OK, based on what I'm reading here and in bug 106336, it sounds like it behaves the same in both quirks and non-quirks now then?
And mentioned on Firefox 13 for developers.