[Cleanup] Remove code related to What's New panel
Categories
(Firefox :: Messaging System, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox126 | --- | fixed |
People
(Reporter: andreio, Assigned: emcminn)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 2 obsolete files)
This messaging surface will not be used anymore and the code is making it difficult for other cleanup tasks like bug 1719463.
Reporter | ||
Comment 1•4 years ago
|
||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
As per product , there is possibility to reuse some of the logic of showing previously shown messages, will be good revisit the cleanup in six months
Updated•3 years ago
|
We can remove this messaging surface. Do note that we might want to reuse some of the logic of showing previously shown messages in the future.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Is there any plan to show "what's new" messages in the enhanced tracking protection panel in the future? We have some messages on train that appear in the protections panel and use the "what's new" panel code, but whose copy doesn't really seem like a "what's new" message. Should these messages be removed? Or should the relevant code just be refactored to remove references to the "what's new" panel?
Comment 7•2 years ago
|
||
This is the message in question. Ed, do you have any thoughts on this? I started removing "what's new" code but it's pretty deeply knotted together with ToolbarPanelHub.jsm, which is necessary for messages like this, which do not seem like "what's new" messages and do not use the What's New panel, but nonetheless share much of the underlying code.
Comment 8•2 years ago
|
||
The protections panel message is still being shown, and that's what caused the delay / comments in the original patch https://phabricator.services.mozilla.com/D122009#3966384 as it wasn't clear if it needed to still be shown or safe to remove.
Seems like we'll probably need to dig into some metrics of people seeing it and clicking learn more. I suppose if it does want to be kept around, the code specific to this protections panel message could be moved into where it gets inserted:
https://searchfox.org/mozilla-central/rev/4cc23dcad1142ec79256f449a55460215fc75498/browser/base/content/browser-siteProtections.js#1665
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•1 year ago
|
||
(In reply to Ed Lee :Mardak from comment #8)
The protections panel message is still being shown, and that's what caused the delay / comments in the original patch https://phabricator.services.mozilla.com/D122009#3966384 as it wasn't clear if it needed to still be shown or safe to remove.
Seems like we'll probably need to dig into some metrics of people seeing it and clicking learn more. I suppose if it does want to be kept around, the code specific to this protections panel message could be moved into where it gets inserted:
https://searchfox.org/mozilla-central/rev/4cc23dcad1142ec79256f449a55460215fc75498/browser/base/content/browser-siteProtections.js#1665
ProtectionPanelMessage was implemented with https://phabricator.services.mozilla.com/D39042. To remove WhatsNewPanel code, a) we should move out ToolbarPanelHub usage in D39042 directly where its inserted inside browser-siteProtections.js
b) Use https://phabricator.services.mozilla.com/D122009 patch to remove only WhatsNewPanel codebase leaving ToolbarBadgeHub which needs product buy-in before removal and can be done separately as shown in patch here
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 10•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 11•11 months ago
|
||
Comment 12•11 months ago
|
||
bugherder |
Updated•10 months ago
|
Description
•