Bug 989130 - Back out changeset fe119a83b1f2 (bug 942017) while leaving the corresponding test from changeset 3c63decb4e7e.  r=jfkthame

This should be backed out for two reasons:

 (1) It caused a serious regression with bullets from list-style-image,
     which no longer affect the line box height and thus overlap.

 (2) The dependency on 'line-height: normal' doesn't make sense; there's
     no reason for whether line-height is 'normal' or not to affect the
     behavior of bullets.

I don't currently have time to figure out why Gecko behavior differs
from other browsers on bug 942017, but that should be re-analyzed and
the bug fixed in a different way.  At first glance, the code should
already be leading to the expected behavior, since the bullet ought to
have the same metrics and alignment as the block's influence on the line
box's height.  Why this isn't the case should be investigated.
Bug 989574 patch 2 - Fix comment to match code.
Bug 989688 patch 1 - Only include the webcomponents reftest.list once.  r=wchen

These duplicate lines were added in two changesets with only one
changeset between them:
https://hg.mozilla.org/mozilla-central/rev/08afb5a033eb
https://hg.mozilla.org/mozilla-central/rev/79b61f9909c0
Bug 989688 patch 2 - Run the reftests in layout/reftests/async-scrolling/.  r=roc

This should have been added in
https://hg.mozilla.org/mozilla-central/rev/a888be20e9d7 (bug 975931).
Bug 989688 patch 3 - Run the reftests in layout/reftests/css-invalid/form/.  r=jwatt

This should have been added in
https://hg.mozilla.org/mozilla-central/rev/7fa9d642fe74 (bug 596515).

jhk, do you still happen to have a copy of the missing
form-dynamic-not-invalid-barred.html file?
Bug 989688 patch 4 - Only include the reftests in layout/reftests/css-valid/output/ once.  r=jwatt

All three lines were added in
https://hg.mozilla.org/mozilla-central/rev/2eb1331a2bc4
Bug 989688 patch 5 - Run the reftests in layout/reftests/view-source/.  r=roc

This should have been added in
https://hg.mozilla.org/mozilla-central/rev/745c0c2aa1fe (bug 464339).

Furthermore, the image being missing was the result of using
checkin-needed on a non-GIT-style diff "containing" an image.

--HG--
rename : layout/reftests/view-source/reftests.list => layout/reftests/view-source/reftest.list
Bug 989688 patch 6 - Run the reftests in toolkit/content/tests/reftests/.  r=enndeakin

This should have been added in
https://hg.mozilla.org/mozilla-central/rev/0c2c2c895e5d (bug 442419) or
perhaps also in bug 841001 when another test was added to this
directory.
Bug 988702 patch 1 - Remove duplication between invalidGradientAndElementValues and the list of invalid values in background-image.  r=heycam

Values that are already in invalidGradientAndElementValues don't also
need to be listed in an array that has invalidGradientAndElementValues
appended to it.
Bug 988702 patch 2 - Test invalid CSS property values for their balanced-ness of () [] or {}.  r=heycam

(This provides an easy mechanism for testing for missing UngetToken()
calls as in the following patch.)
Bug 988702 patch 3 - Fix missing UngetToken() calls in ParseCounterData(), and avoid evil CheckEndProperty() calls while I'm there.  r=heycam

I tested that test_property_syntax_errors.html gives a failure on the
new test without the patch, and that the failure is not present with the
patch.
Bug 989560 patch 1 - Make it an error to have an empty item within an animation or transition shorthand.  r=heycam

This is needed to make the test in the next patch (which tests that we
reject entirely-empty properties) pass.
Bug 989560 patch 2 - Don't accept an empty value for font-variant-alternates.  r=heycam

Had patch 3 not been present, this would be needed to prevent a test
failure with patch 4 (which removes the ExpectEndProperty check from the
CSS_PROPERTY_PARSE_VALUE case in
CSSParserImpl::ParseProperty(nsCSSProperty) since its callers handle
checking for appropriate endings), since the way this function returns
success for empty values leads var() functions alone inside
font-variant-alternates to be rejected, since
CSSParserImpl::ParseProperty(nsCSSProperty) won't try reparsing with
variables.
Bug 989560 patch 3 - Add one more ExpectEndProperty() call that is needed for variables.  r=heycam

This adds a check that is currently present in most but not all
codepaths leading to this point, but which patch 4 will remove from many
of those codepaths.
Bug 989560 patch 4 - Remove most uses of CheckEndProperty()/ExpectEndProperty().  r=heycam