Clean up layout debug APIs

NEW
Unassigned

Status

()

16 years ago
6 months ago

People

(Reporter: sfraser_bugs, Unassigned)

Tracking

Trunk
PowerPC
macOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
We have a mess of debug APIs now:

The debug component, over in extensions/layout-debug, has nsIDebugObject.
The layout code, in layout/base/public, has nsILayoutDebugger.

In addition, some debug stuff doesn't use either API, e.g.
nsIPresShell->SetPaintFrameCount().

I see no reason to maintain the layout-debug extension. Since the code is
debug-only, we should just put it in layout.
(Reporter)

Comment 1

16 years ago
Of course there is nsIFrameDebug too.
->misc code
Component: Layout → Layout: Misc Code
(Reporter)

Updated

10 years ago
Assignee: sfraser_bugs → nobody
QA Contact: ian → layout.misc-code

Updated

6 months ago
Product: Core → Core Graveyard
(Assignee)

Updated

6 months ago
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.