The binding itself looks pretty easy: https://bgrins.github.io/xbl-analysis/tree/#richlistitem. I assume the tricky part will be covering inherited bindings at the same time. That might have to happen all at once, and there may be some flattening there that could happen as well (like the autocomplete-profile-* bindings).
It doesn't look like the base richlistitem does much on connection so I don't anticipate perf problems on that. But some of the inherited bindings set <content>, so if there are hidden instances of those there could be potential regressions.
Here's a try push that does just the base binding: https://treeherder.mozilla.org/#/jobs?repo=try&revision=977c38236965e5f22959f89ef83626604595874e&selectedJob=215748047
Depends on: 1519498
You need to log in before you can comment on or make changes to this bug.