(In reply to Marco Castelluccio [:marco] from comment #1) > Maybe this is the same as bug 1778692? Could you find the regression range in bug 1778692? > > (In reply to Adrian Florinescu [:aflorinescu] from comment #0) > > **Note** > > * Not sure how reliable is but mozgression find fix points towards bug 1772941. > > Most likely it isn't right. If it is the same as bug 1778692, then the fix is in bug 1778827. I can't confirm or infirm based on mozregression find fix - it is still pointing towards bug 1772941, but given that is a backout, I was guessing that it is mostly likely wrong. Indeed bug 1778827 seems more likely to be the fixing issue.
Bug 1779742 Comment 2 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 Marco Castelluccio [:marco] from comment #1) > Maybe this is the same as bug 1778692? Could you find the regression range in bug 1778692? > > (In reply to Adrian Florinescu [:aflorinescu] from comment #0) > > **Note** > > * Not sure how reliable is but mozgression find fix points towards bug 1772941. > > Most likely it isn't right. If it is the same as bug 1778692, then the fix is in bug 1778827. I can't confirm or infirm based on mozregression find fix - it is still pointing towards bug 1772941, but given that found commit message is a backout, I was guessing that it is mostly likely wrong. Indeed bug 1778827 seems more likely to be the fixing issue.