Every time I look at that page, I'm heartened by the part at the top that says "Modified: 4 days ago". It makes me hope that maybe the bug is being worked on after all. But I found the page's history link: https://bugzilla.mozilla.org/show_activity.cgi?id=1215064 and I think that those "CC" updates are only people signing up to be notified about changes to the bug's status. Sigh.
From https://www.mediawiki.org/wiki/Bugzilla/Fields#CC_/_CC_List: CC / CC List This field will add people to a mailing list which notifies users when a bug has been changed. It's generally not a good idea to add people other than yourself to the CC list unless you know that they welcome such notifications.
I don't know what the difference (if any) is between "changes to the bug's status" and "when a bug has been changed". Does "change" indicate its description, scope, or what someone feels is needed to close it has been modified somehow? Does it mean it's actually being worked on so progress is being made? Yay, vagueness...
I still haven't tried out the example in the 2nd link, for add-on buttons.
Yeah, that's why this is my backburner project - when I get into the CSS, I want to see what happens when I use the workaround(s) to add the add-on buttons in. I imagine on some level I'm either going to think it's a disaster by my standards, and/or that having the buttons is useless because they don't work.
Either state's either going to stop my project altogether or else require extra fiddling to carry on until I can live with the results. I haven't even gotten back to modifying an add-on that needs some work (I simply stopped using it in the meantime, because it's hard to see it and *not work on it* - I get that itch so bad, but just don't have time right now).
no subject
From https://www.mediawiki.org/wiki/Bugzilla/Fields#CC_/_CC_List:
CC / CC List This field will add people to a mailing list which notifies users when a bug has been changed. It's generally not a good idea to add people other than yourself to the CC list unless you know that they welcome such notifications.
I don't know what the difference (if any) is between "changes to the bug's status" and "when a bug has been changed". Does "change" indicate its description, scope, or what someone feels is needed to close it has been modified somehow? Does it mean it's actually being worked on so progress is being made? Yay, vagueness...
I still haven't tried out the example in the 2nd link, for add-on buttons.
Yeah, that's why this is my backburner project - when I get into the CSS, I want to see what happens when I use the workaround(s) to add the add-on buttons in. I imagine on some level I'm either going to think it's a disaster by my standards, and/or that having the buttons is useless because they don't work.
Either state's either going to stop my project altogether or else require extra fiddling to carry on until I can live with the results. I haven't even gotten back to modifying an add-on that needs some work (I simply stopped using it in the meantime, because it's hard to see it and *not work on it* - I get that itch so bad, but just don't have time right now).