Closed Bug 1331994 Opened 7 years ago Closed 7 years ago

Back out bug 1300374 for Firefox 51

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox51 --- fixed
firefox52 --- affected
firefox53 --- affected

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

Details

Attachments

(1 file)

See bug 1300374 comment 22.  The PR aspects of this suck, but since Hixie is being obstinate and this is not really blocking anything yet in practice...
I thought we were going to write a patch to disable it. I am a bit concerned that we will disable non trivial patch in rc2 without pre release channel testing
This is just a straight backout of the C++ parts, plus the failure annotations for the tests; seemed simpler than backing out the tests
Attachment #8828022 - Flags: review?(emilio+bugs)
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Sylvestre,

The patch in question (bug 1300374) basically removed some null-checks.  Disabling it just means putting them back.

This is restoring the behavior Firefox 50 has, as well as the behavior Chrome currently has, so I think the risk is _extremely_ low...
Comment on attachment 8828022 [details] [diff] [review]
Back out the fix for bug 1300374 from Firefox 51 for now, while we wait for Acid3 to be updated to the spec changes

Review of attachment 8828022 [details] [diff] [review]:
-----------------------------------------------------------------

r=me. The patch could've been a bit more minimal (just touching the two nsCSSRuleProcessor.cpp functions and the test lists), but this is ok too :)
Attachment #8828022 - Flags: review?(emilio+bugs) → review+
And yeah, I agree that this is really low risk to take.
OK, thanks. Please land that in m-r asap then :)
(or ping a sheriff)
Comment on attachment 8828022 [details] [diff] [review]
Back out the fix for bug 1300374 from Firefox 51 for now, while we wait for Acid3 to be updated to the spec changes

Approval Request Comment
[Feature/Bug causing the regression]: Bug 1300374
[User impact if declined]: None for actual user experience.  The main impact
   would be bad press around the Acid3 stuff.
[Is this code covered by automated tests?]:  Yes.
[Has the fix been verified in Nightly?]:  No.  However, this is a straight
   backout which applied cleanly, and restores the Firefox 50 behavior (and the
   current Chrome behavior).
[Needs manual test from QE? If yes, steps to reproduce]: No.  I did check that
   this fixes the Acid3 issue we're worrying about.
[List of other uplifts needed for the feature/fix]: None.
[Is the change risky?]: In my opinion, no.  See above about verification.
[Why is the change risky/not risky?]: See above.
[String changes made/needed]: None.
Attachment #8828022 - Flags: approval-mozilla-beta?
Comment on attachment 8828022 [details] [diff] [review]
Back out the fix for bug 1300374 from Firefox 51 for now, while we wait for Acid3 to be updated to the spec changes

51 is now on m-c
By the way, I guess this is impacting fennec too, right?
Attachment #8828022 - Flags: approval-mozilla-beta? → approval-mozilla-release+
I assume you mean "m-r".  ;)

Pushed, hopefully to the right place: https://hg.mozilla.org/releases/mozilla-release/rev/1f694d0ba1e8cbfd7d87c27946c95ed326dd85bf

Yes, this affects fennec too.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
yeah, sorry, long day :)
I'll be starting the build for fennec and desktop RC2 later today.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: