In the interest of TB 78 reputation and user acceptance, I'm proposing to fast-track this much-demanded feature using this patch, which can easily be uplifted into TB 78: no new prefs, no c++ code, no translations. (In reply to Thomas D. (:thomas8) from comment #59) > [snip] > **I'm worried that we're not delivering this important and much-demanded > feature to users as fast as possible. Lots of users have identified this as > a painpoint of TB 78, so fast delivery will be in our best interest.** > I like Paenglab's idea in comment 28 of landing my patch as a fast fix for > TB 78 and gain time to craft a more elaborate fix. > Fwiw, my patch does not need new prefs, c++ code or translations and I > believe it was covering all CC/BCC scenarios at a very low cost of > implementation. I think it's easily maintainable even when we add a more > elaborate solution later. I've laid out my ideas for a more comprehensive and versatile, but still low-cost solution in the first part of comment 59.
Bug 1616514 Comment 60 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In the interest of TB 78 reputation and user acceptance, I'm proposing to fast-track this much-demanded feature using this patch, which can easily be uplifted into TB 78: no new prefs, no c++ code, no translations. (In reply to Thomas D. (:thomas8) from comment #59) > [snip] > **I'm worried that we're not delivering this important and much-demanded > feature to users as fast as possible. Lots of users have identified this as > a painpoint of TB 78, so fast delivery will be in our best interest.** > I like Paenglab's idea in comment 28 of landing my patch attachment 9178125 [details] [diff] [review] as a fast fix for > TB 78 and gain time to craft a more elaborate fix. > Fwiw, my patch does not need new prefs, c++ code or translations and I > believe it was covering all CC/BCC scenarios at a very low cost of > implementation. I think it's easily maintainable even when we add a more > elaborate solution later. I've laid out my ideas for a more comprehensive and versatile, but still low-cost solution in the first part of comment 59.
In the interest of TB 78 reputation and user acceptance, I'm proposing to fast-track this much-demanded feature using this patch, which can easily be uplifted into TB 78: no new prefs, no c++ code, no translations. (In reply to Thomas D. (:thomas8) from comment #59) > [snip] > **I'm worried that we're not delivering this important and much-demanded > feature to users as fast as possible. Lots of users have identified this as > a painpoint of TB 78, so fast delivery will be in our best interest.** > I like Paenglab's idea in comment 28 of landing my patch attachment 9178125 [details] [diff] [review] > as a fast fix for TB 78 and gain time to craft a more elaborate fix. > Fwiw, my patch does not need new prefs, c++ code or translations and I > believe it was covering all CC/BCC scenarios at a very low cost of > implementation. I think it's easily maintainable even when we add a more > elaborate solution later. I've laid out my ideas for a more comprehensive and versatile, but still low-cost solution in the first part of comment 59.