Opened 22 months ago
Closed 3 months ago
#25311 closed defect (fixed)
Check that #18900 is still fixed
Reported by: | arthuredelstein | Owned by: | tbb-team |
---|---|---|---|
Priority: | Medium | Milestone: | |
Component: | Applications/Tor Browser | Version: | |
Severity: | Normal | Keywords: | ff68-esr, tbb-update, TorBrowserTwam201909 |
Cc: | mcs, brade | Actual Points: | |
Parent ID: | Points: | ||
Reviewer: | Sponsor: | Sponsor44-can |
Description
In https://bugzilla.mozilla.org/show_bug.cgi?id=1434666 we checked in a patch that is supposed to fix the problem seen in #18900. But we should run at least a manual regression test to see that this indeed fixed the bug, and we don't need our #18900 patch any more for TBB/ESR60.
Child Tickets
Change History (4)
comment:1 Changed 16 months ago by
Keywords: | ff68-esr added; ff60-esr removed |
---|
comment:3 follow-up: 4 Changed 3 months ago by
Keywords: | tbb-update TorBrowserTwam201909 added |
---|---|
Status: | new → needs_information |
mcs/brade: We are good here, right?
comment:4 Changed 3 months ago by
Resolution: | → fixed |
---|---|
Status: | needs_information → closed |
Note: See
TracTickets for help on using
tickets.
The patch in https://bugzilla.mozilla.org/show_bug.cgi?id=1434666 got backed out (https://hg.mozilla.org/mozilla-central/rev/505bafeafb66b0083ce1fca8eec2d061f1a5ebb7) and we are still shipping our patch for #18900. Thus, nothing to verify here. Moving to ff68-esr.