> although authors can update their themes > It is just unrealistic. At least such drastic changes about the appearance of themes should be communicated on blog.mozilla.org/addons and maybe other channels a few weeks *before* such changes land in a stable release of Firefox so that theme authors have a chance to do the necessary changes. I think the bigger problem as the change itself (you can never make everyone happy) is that it was a surprise. Of course it's not realistic that *every* theme author will update their theme (and maybe some theme authors even think that it's a good change for their theme). But it's really important that at least extension developers and theme authors *can* react before their users are affected by a "breaking" product change. And I would argue that such a visible change of a theme is kind of a "breaking change" from the point of view of a theme developer. And it would also have been helpful for the support community to know about this before we got surprised by the affected users. So regardless of whether there will be a product change or not - maybe you could include the topic communication in your post mortem about Firefox 96 to prevent similar situations in the future. Thank you!
Bug 1746000 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> although authors can update their themes > It is just unrealistic. At least such drastic changes about the appearance of themes should be communicated on blog.mozilla.org/addons and maybe other channels a few weeks *before* such changes land in a stable release of Firefox so that theme authors have a chance to do the necessary changes. I think the bigger problem as the change itself (you can never make everyone happy) is that it was a surprise. Of course it's not realistic that *every* theme author will update their theme (and maybe some theme authors even think that it's a good change for their theme). But it's really important that at least extension developers and theme authors *can* react before their users are affected by a "breaking" product change. And I would argue that such a visible change of a theme is kind of a "breaking change" from the point of view of a theme developer. And it would also have been helpful for the support community to know about this before we got surprised by the affected users. So regardless of whether there will be another product change or not - maybe you could include the topic communication in your post mortem about Firefox 96 to prevent similar situations in the future. Thank you!