Bug 1621274 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 Mats Palmgren (PTO) from comment #21)
> Our goal is to remove XUL layout ASAP.  The solution to this bug is for TB to stop using XUL and instead use CSS display types.
> I think this bug should be resolved as WONTFIX.  "Fixing" minor issues like this in DEBUG builds is simply not a problem we should expend any resources on whatsoever. It's counterproductive since we could have spent this time on bugs that matter instead. :-(

Can we simply add the patch to the M-C tree?
The patch here is simply suppress the stacktrace for known XULBox case, and it is already shown to work.

The sheer amount of stack trace from the assert adds almost 2MB to debug log and really a pain to wade through  and **makes it difficult to analyze  the bugs that matter**. The patch eliminates the stack trace.

So what should I to push the patch to be adopted to M-C tree?
(In reply to Mats Palmgren (PTO) from comment #21)
> Our goal is to remove XUL layout ASAP.  The solution to this bug is for TB to stop using XUL and instead use CSS display types.
> I think this bug should be resolved as WONTFIX.  "Fixing" minor issues like this in DEBUG builds is simply not a problem we should expend any resources on whatsoever. It's counterproductive since we could have spent this time on bugs that matter instead. :-(

Can we simply add the patch to the M-C tree?
The patch here is simply suppress the stacktrace for known XULBox case, and it is already shown to work.

The sheer amount of stack trace from the assert adds almost 2MB to debug log (dwindled somewhat lately) and really is a pain to wade through  and **makes it difficult to analyze  the bugs that matter**.  The patch eliminates the stack trace.

So what should I to push the patch to be adopted to M-C tree?

Back to Bug 1621274 Comment 22