Move Protection Panel Message to calling code
Categories
(Firefox :: Messaging System, enhancement, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: pdahiya, Assigned: emcminn)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [omc])
Attachments
(1 file)
Scope of this bug is move PROTECTION_PANEL message to directly where its inserted inside
browser-siteProtections.js
See https://bugzilla.mozilla.org/show_bug.cgi?id=1724300#c9
This will unblock removing WhatsNewPanel code base and devtool whats new panel test messages from messaging system that's no longer supported
Reporter | ||
Updated•1 year ago
|
Reporter | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Romain, do you know who will own the Protections Panel message once it's been moved into browser-siteProtections.js
? The folks I know of who worked on it originally aren't around anymore. I'm also curious who I should check in with about the telemetry - in the attached patch I've created a recordEvent
ping that kind of duplicates the old Messaging System telemetry, but it required adding some keys to the existing schema and I want to make sure that's OK!
Comment 3•1 year ago
|
||
Hi Emily, I'm not sure but NIing Tim and Paul who may know.
Comment 4•1 year ago
|
||
Paul is currently the owner of the protection panel.
Updated•1 year ago
|
Reporter | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Backed out for causing mochitests failures in browser_protectionsUI.js.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | browser/base/content/test/protectionsUI/browser_protectionsUI.js | Test timed out -
Assignee | ||
Comment 7•1 year ago
|
||
I've opted to remove the check for telemetry from the new test added to browser_protectionsUI.js
; on top of it being kinda flaky itself, it also had a tendency to cause other tests looking at the telemetry to throw.
I’m also going to revert the use of BrowserTestUtils.waitForMutationCondition
back to TestUtils.waitForCondition
- some of the failures were caused by that promise hanging and never returning, plus all the other tests in the file use TestUtils.waitForCondition
.
I've filed bug 1874024 to cover these, and will try to land the cleaned up patch this afternoon.
Comment 9•1 year ago
|
||
If you prefer you can also move your test to a separate file. Working around any timeout or intermittent issues with the existing test. Currently looking to reduce failures of this test in another bug.
Comment 10•1 year ago
|
||
bugherder |
Assignee | ||
Updated•1 year ago
|
Description
•