Closed
Bug 1496827
Opened 7 years ago
Closed 7 years ago
Remove the "notification" binding
Categories
(Toolkit :: UI Widgets, task, P1)
Toolkit
UI Widgets
Tracking
()
RESOLVED
FIXED
mozilla65
Tracking | Status | |
---|---|---|
firefox65 | --- | fixed |
People
(Reporter: bgrins, Assigned: Paolo)
References
Details
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #1471403 +++
We had some discussion about this at https://mozilla.logbot.info/fx-team/20181005#c15423019, so figured I'd get a bug on file for it. This would help make conversion to Fluent possible for notification.
This needs more investigation, but if the notifications are only ever created from within the notificationbox or at least a limited set of places it's possible we could build the entire DOM up directly under that node instead of slotting in child nodes into the [anonid="details"] element: https://searchfox.org/mozilla-central/rev/807a37c670c093b6e5201841a7c5315ba67ba8d5/toolkit/content/widgets/notification.xml#397.
We could do that either with a Custom Element (which would allow us to translate the properties/methods as in https://github.com/bgrins/xbl-analysis/blob/gh-pages/elements/generated/Notification.js), or move all the logic up into notificationbox.
Assignee | ||
Updated•7 years ago
|
Summary: Investigate how to remove XBL for <notification> → Remove the "notification" binding
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → paolo.mozmail
Status: NEW → ASSIGNED
Priority: P5 → P1
Assignee | ||
Comment 2•7 years ago
|
||
We may still have to update tests or production code that customizes the notifications, running a tryserver build here:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=d5d54ed862b50078e43382df9244f0af3ed7fc93
Assignee | ||
Comment 3•7 years ago
|
||
Assignee | ||
Comment 4•7 years ago
|
||
Reporter | ||
Comment 5•7 years ago
|
||
Heads up that more notification changes are incoming (this is follow on to the work at bug 1471403). This is a Custom Element conversion so that part should work straight away, but a number of tests are needing to be updated (things that dig into anon content, some property accesses switching to attribute lookups, etc). See https://phabricator.services.mozilla.com/D11650.
Flags: needinfo?(jorgk)
Comment 6•7 years ago
|
||
Apparently we've already forked the binding and will de-XBL it later. Magnus, is anything required here?
Flags: needinfo?(jorgk) → needinfo?(mkmelin+mozilla)
Reporter | ||
Comment 7•7 years ago
|
||
You'll probably need to rename the XBL'ed element from <notification> to something else so that you don't end up with both XBL and a Custom Element attached to it after this bug lands.
Pushed by paolo.mozmail@amadzone.org:
https://hg.mozilla.org/integration/mozilla-inbound/rev/91320b1c87ce
Remove the "notification" binding. r=bgrins
Comment 10•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
Updated•7 years ago
|
Flags: needinfo?(mkmelin+mozilla)
Updated•6 years ago
|
Type: enhancement → task
You need to log in
before you can comment on or make changes to this bug.
Description
•