Closed Bug 1783783 Opened 3 years ago Closed 3 years ago

Null dereference in some chrome frames when CSS named pages is enabled

Categories

(Core :: Layout, defect, P2)

Product:
Core
Component:
Layout
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
105 Branch
Tracking Flags:
Tracking Status
firefox105 --- fixed

People

(Reporter: alaskanemily, Assigned: alaskanemily)

References

Details

Attachments

(1 file)

Bug 1783783 - Add null-check for aParentFrame when computing used page values in nsCSSFrameConstructor
48 bytes, text/x-phabricator-request
Details | Review

Can be seen here when testing for unexpected failures/successes with CSS named pages enabled: https://treeherder.mozilla.org/jobs?repo=try&revision=bf4effc2e8e53fbebe04404affac7cc520844ca5&selectedTaskRun=TfBu0-u9QXCKxBgUj1pFAg.0

Pushed by emcdonough@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/21e5f4ad7f75 Add null-check for aParentFrame when computing used page values in nsCSSFrameConstructor r=dholbert

https://hg.mozilla.org/mozilla-central/rev/21e5f4ad7f75

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox105: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: