Closed Bug 1493680 Opened 7 years ago Closed 7 years ago

[performance-new] The preferences are not saved anymore

Categories

(DevTools :: Performance Tools (Profiler/Timeline), defect, P1)

defect

Tracking

(firefox-esr60 unaffected, firefox62 unaffected, firefox63 fixed, firefox64 fixed)

RESOLVED FIXED
Firefox 64
Tracking Status
firefox-esr60 --- unaffected
firefox62 --- unaffected
firefox63 --- fixed
firefox64 --- fixed

People

(Reporter: julienw, Assigned: julienw)

References

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

Bug 1222047 changed how the preference front is retrieved. The problem is that it's now a promise, and our code doesn't account for this.
Blocks: 1222047
STR is simple: 1. enable the new performance panel from devtools settings, and restart the devtools. 2. open the performance panel. 3. change the preferences from the default ones. 4. close devtools, open the performance panel again. => look at how the preferences are back to default.
I'd like to track this for 63. It's not important or even impactful for end-users because the panel isn't enabled by default, but it can be important for gecko developers doing some remote profiling on 63.
Assignee: nobody → felash
Priority: -- → P1
Attachment #9011483 - Attachment is obsolete: true
Comment on attachment 9011484 [details] Bug 1493680 - use the new getFront API and properly wait for the promise fullfilment Greg Tatum [:gregtatum] has approved the revision.
Attachment #9011484 - Flags: review+
Comment on attachment 9011484 [details] Bug 1493680 - use the new getFront API and properly wait for the promise fullfilment Approval Request Comment [Feature/Bug causing the regression]: bug 1222047 [User impact if declined]: end-user: none; but gecko developers won't be able to change the preferences for the profiler in a remote setting. [Is this code covered by automated tests?]: no [Has the fix been verified in Nightly?]: yes [Needs manual test from QE? If yes, steps to reproduce]: no [List of other uplifts needed for the feature/fix]: none [Is the change risky?]: no [Why is the change risky/not risky?]: because the code is not exposed to end-users [String changes made/needed]: none
Attachment #9011484 - Flags: approval-mozilla-beta?
Pushed by jwajsberg@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d3d5149546bf use the new getFront API and properly wait for the promise fullfilment r=gregtatum
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 64
Comment on attachment 9011484 [details] Bug 1493680 - use the new getFront API and properly wait for the promise fullfilment Low risk as this is not exposed to end-users, uplift approved for 63 beta 10, thanks.
Attachment #9011484 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: