Expose getBoxObjectFor on Document instead of XULDocument

RESOLVED FIXED in Firefox 63

Status

()

enhancement
RESOLVED FIXED
9 months ago
a month ago

People

(Reporter: bgrins, Assigned: bgrins)

Tracking

(Blocks 1 bug)

unspecified
mozilla63
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

9 months ago
This will help narrow the gap between XUL docs and HTML docs. The functionality itself is already implemented as nsIDocument::GetBoxObjectFor, so I believe this will be more-or-less a webidl change (exposed to `[Func="IsChromeOrXBL"]` in Document.webidl).

https://searchfox.org/mozilla-central/rev/033d45ca70ff32acf04286244644d19308c359d5/dom/webidl/XULDocument.webidl#35-36
(Assignee)

Updated

9 months ago
Assignee: nobody → bgrinstead
Status: NEW → ASSIGNED
(Assignee)

Updated

9 months ago
Blocks: 1480168
Comment on attachment 8996357 [details]
Bug 1479543 - Expose getBoxObjectFor on Document instead of XULDocument;r=bz

Boris Zbarsky [:bz] (no decent commit message means r-) has approved the revision.

https://phabricator.services.mozilla.com/D2570
Attachment #8996357 - Flags: review+

Comment 3

9 months ago
Pushed by bgrinstead@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f32aa04aee9c
Expose getBoxObjectFor on Document instead of XULDocument;r=bzbarsky

Comment 4

9 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/f32aa04aee9c
Status: ASSIGNED → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Component: DOM → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.