No changes to the transition manager are needed since
nsTransitionManager::StyleContextChanged already makes the appropriate
calls to ConsiderStartingTransition for 'all', and that existing code
should work fine within a loop (just like the existing code to handle
shorthands or other property duplication works).
This adds entries for property aliases as though they are shorthands.
This fits with the CSS working group's recent resolution to describe
aliases as shorthands, recorded in
http://lists.w3.org/Archives/Public/www-style/2012Aug/0770.html .
The property_database.js entries themselves are copied from the
non-alias entries for the properties, with these changes:
(1) The property name is changed to the prefixed form
(2) The domProp entry is changed to the prefixed form
(3) Adding alias_for entries for each property.
(4) When type is CSS_TYPE_LONGHAND in the target of the alias, type for
the alias is CSS_TYPE_SHORTHAND_AND_LONGHAND and a subproperties
entry is added with the target of the alias.
There are also some indentation fixes to the copied entries in
property_database.js (made before they were copied, and thus affecting
the original as well).
This currently only affects the testing of overflow, but it will also
affect -moz-transform (and any other aliases implemented the same way)
after the later patches in this bug.
This special-cases text-decoration because text-decoration: inherit causes
the color to inherit in a way that we can't serialize the result (since
it's no longer "foreground"). (This isn't great; we might want to
consider fixing it somehow.)
This changes test_property_syntax_errors.html in the following ways:
(1) removes the "known failures" handling, since there aren't any
(2) changes it to test syntax errors in both quirks mode and standards
mode, instead of only in standards mode
(3) uses a (new) quirks_values mechanism to property_database.js to
test cases that should be invalid in standards mode but accepted in
quirks mode
This changes test_property_syntax_errors.html in the following ways:
(1) removes the "known failures" handling, since there aren't any
(2) changes it to test syntax errors in both quirks mode and standards
mode, instead of only in standards mode
(3) uses a (new) quirks_values mechanism to property_database.js to
test cases that should be invalid in standards mode but accepted in
quirks mode
This also converts all of the tests in layout/style/test/ to using
calc(), except that it duplicates all of the valid values and some of
the invalid values for 'width' and '-moz-column-rule-width' (which are
the two properties that intentionally have extensive calc() tests) in
property_database.js.
