Bug 1734912 Comment 22 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to mdcclxv from comment #19)
> ...
> I can't believe what I'm reading. So screw'em, right?! Because that's definitely what you are implying! Let's do that to the wheelchair folks. Let's do the Alzheimer people. Majority rules, minority ... who cares?! First time when you find yourself in a minority just remember what you said here.

He said nothing of the sort.  Please be respectful in bugzilla.

Sometimes graphics issues affecting Thunderbird don't get detected until late in a development cycle, or in this case even after release, sometimes because we exercise core code that is less used or more obsolete for Firefox.  I'm not sure that's the case here, but it's nothing new.   

Regardless, the key to progress is without a lot of drama to identify the issue, see if it's been reported before, and get it before the right people. I've started a quick examination of core graphics and the good news is so far I don't see any wontfixed bug reports.  After we have that assessment we look to see if anything can be done about it.  

If someone knows of an already confirmed unfixed bug report please cite it. Else, have a look at this list of 32 core graphics bug reports going back 5 years https://mzl.la/3voXNSZ
(In reply to mdcclxv from comment #19)
> ...
> I can't believe what I'm reading. So screw'em, right?! Because that's definitely what you are implying! Let's do that to the wheelchair folks. Let's do the Alzheimer people. Majority rules, minority ... who cares?! First time when you find yourself in a minority just remember what you said here.

He said nothing of the sort.  Please be respectful in bugzilla.

Sometimes graphics issues affecting Thunderbird don't get detected until late in a development cycle, or in this case even after release, sometimes because we exercise core code that is less used or more obsolete for Firefox.  I'm not sure that's the case here, but it's nothing new.   

Regardless, the key to progress is without a lot of drama to identify the issue, see if it's been reported before, and get it before the right people. I've started a quick examination of core graphics and the good news is so far I don't see any wontfixed bug reports.  After we have that assessment we look to see if anything can be done about it.  

If someone knows of an already confirmed, relevant unfixed bug report please cite it. Else, have a look at this list of 32 core graphics bug reports going back 5 years https://mzl.la/3voXNSZ

Back to Bug 1734912 Comment 22