Closed Bug 1586175 Opened 2 months ago Closed 2 months ago

back out bug 1351924 for Firefox 70


(Core :: Layout, task)

70 Branch
Not set



Tracking Status
firefox70 ? fixed


(Reporter: dbaron, Unassigned)



(2 files)

I'd like to back out bug 1351924 for Firefox 70, because of regression bug 1584018 and the possibility of other sites being broken due to the same bug, since I think it's better not to try landing the fixes this late in the cycle. But I'd like to to this backout only on beta so that we can continue moving forwards on nightly.

I'm not entirely sure what the procedure for a backout only-on-beta is these days, given the phabricator/lando workflow we mostly use now.

I'm also going to be away and probably not around to help with this, but I'm hoping that dholbert could help if needed.

Comment on attachment 9098885 [details] [diff] [review]
backout patch

Beta/Release Uplift Approval Request

  • User impact if declined: regressions such as bug 1584018
  • Is this code covered by automated tests?: Unknown
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): reverting to the state in the previous release
  • String changes made/needed: no
Attachment #9098885 - Flags: approval-mozilla-beta?
Comment on attachment 9098885 [details] [diff] [review]
backout patch

Backout, includes test changes. Let's land this on beta only for beta 13.
Attachment #9098885 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Thanks, Liz!

Let me know if we should land this manually.

(Last I checked, there are dedicated folks who land beta-approved patches, on a timeframe that works well for RelEng, so I'm assuming that'll happen here, but correct me if that's changed & we should take action to land it.)

We also need to backout the test that landed in bug 1576864 (which is expected to fail without bug 1351924's fix), to avoid perma-orange.

I'll post a patch to do that shortly.

Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.