Closed Bug 1692677 Opened 5 years ago Closed 5 years ago

tb debug perma assertion failure: !disp->IsAbsolutelyPositionedStyle() || disp->DisplayInside() != StyleDisplayInside::MozBox (was blockified but isn't any longer! It probably needs explicit 'display:block' ), at layout/base/nsCSSFrameConstructor.cpp:5545

Categories

(Thunderbird :: Message Compose Window, defect, P5)

Tracking

(thunderbird_esr78 unaffected)

RESOLVED FIXED
87 Branch
Tracking Status
thunderbird_esr78 --- unaffected

People

(Reporter: intermittent-bug-filer, Assigned: aleca)

References

(Regression)

Details

(Keywords: assertion, intermittent-failure)

Attachments

(1 file)

Assertion failure: !disp->IsAbsolutelyPositionedStyle() || disp->DisplayInside() != StyleDisplayInside::MozBox (This may be a frame that was previously blockified but isn't any longer! It probably needs explicit 'display:block' to preserve behavior), at /builds/worker/checkouts/gecko/layout/base/nsCSSFrameConstructor.cpp:5545

Something changed with https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=668376949c26fc346f02e74a40836ad999172dc4

It seems that the tests in question all involve a compose window.

Component: Add-Ons: General → Message Compose Window

Backout of https://hg.mozilla.org/comm-central/rev/8bb80263dee66803a38e74bc0bca714a1ab3620d fixes it. I'm not going to do that just yet as I'm not that worried about debug BCT failures. Now to figure out why.

Regressed by: 1640760
Summary: Assertion failure: !disp->IsAbsolutelyPositionedStyle() || disp->DisplayInside() != StyleDisplayInside::MozBox (was blockified but isn't any longer! It probably needs explicit 'display:block' ), at layout/base/nsCSSFrameConstructor.cpp:5545 → tb debug perma assertion failure: !disp->IsAbsolutelyPositionedStyle() || disp->DisplayInside() != StyleDisplayInside::MozBox (was blockified but isn't any longer! It probably needs explicit 'display:block' ), at layout/base/nsCSSFrameConstructor.cpp:5545

Likely replacing #attachmentInfo with a div and the children with span/div will magically sort this out.
Maybe the dev tools can could tell which of the involved elements have the wrong characteristics.

Ouch, sorry for the issue.
I'll take care of this.

Assignee: nobody → alessandro
Status: NEW → ASSIGNED

Converting those elements in HTML seems to do the trick like Magnus said: https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=8b6849d0b25145cc6acb384cbba89933d89f1a4f

Patch incoming.

Attachment #9203510 - Flags: review?(geoff)
Attachment #9203510 - Flags: review?(geoff) → review+

Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/08ae9df8f829
Fix Assertion failure due to absolute positioned -moz-box element. r=darktrojan

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch

Breadcrumb trail. I can't imagine this exact bug would pop up again, but just in case...
Over in Bug 1693435 I wrote up some steps to trigger it .

Regressions: 1753824
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: