Closed
Bug 647273
Opened 14 years ago
Closed 14 years ago
Remove nsIContentUtils
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
FIXED
People
(Reporter: justin.lebar+bug, Assigned: justin.lebar+bug)
References
(Blocks 1 open bug)
Details
(Whiteboard: [cleanup])
Attachments
(1 file, 2 obsolete files)
26.77 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
Now that non-libxul builds are unsupported, my understanding is that nsIContentUtils doesn't serve a useful purpose and can be removed.
And nsIContentUtils2, and maybe nsIContentUtils3 if we managed to grow that ... But yes, as long as the interface was only to allow it to be used cross-module (and there are no script consumers) you can scrap it.
Assignee | ||
Comment 2•14 years ago
|
||
How does this look to you, Jonas?
Attachment #525222 -
Flags: review?(jonas)
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → justin.lebar+bug
Assignee | ||
Comment 3•14 years ago
|
||
Unbitrotting after removal of a MOZILLA_2_0 interface.
Attachment #525593 -
Flags: review?(jonas)
Assignee | ||
Updated•14 years ago
|
Attachment #525222 -
Attachment is obsolete: true
Attachment #525222 -
Flags: review?(jonas)
Assignee | ||
Comment 4•14 years ago
|
||
Removing nsLayoutModule entries, which I initially missed.
Attachment #525614 -
Flags: review?(jonas)
Assignee | ||
Updated•14 years ago
|
Attachment #525593 -
Attachment is obsolete: true
Attachment #525593 -
Flags: review?(jonas)
Attachment #525614 -
Flags: review?(jonas) → review+
Comment 5•14 years ago
|
||
This landed: http://hg.mozilla.org/mozilla-central/rev/457757151653 and broke Windows builds: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1302810160.1302813617.29925.gz and got backed out as a result: http://hg.mozilla.org/mozilla-central/rev/026fc72b77aa
Assignee | ||
Comment 6•14 years ago
|
||
So the problem is TestChromeMargin.cpp, a Windows only cpp test. It tests a function in ns{I}ContentUtils. If you include nsContentUtils.h directly, you end up including enough of the world that you need to be in the internal API world. But I can't figure out how to get this unit test into that world. Apparently you can't just #define MOZILLA_INTERNAL_API and expect things to work. :) jimm or someone else: Any ideas on how to fix this? I'd really hate to hold this bug up on a test technicality.
Assignee | ||
Comment 7•14 years ago
|
||
On IRC, jimm gave me r+ to disable widget/tests/TestChromeMargin.cpp. I'll file a followup bug to fix and re-enable the test.
Assignee | ||
Comment 8•14 years ago
|
||
Pushed with misbehaving test disabled: http://hg.mozilla.org/mozilla-central/rev/863db843fde4
Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•