Open Bug 114726 Opened 24 years ago Updated 3 years ago

platform-specific contractIDs in widget

Categories

(Core :: Widget, defect, P3)

defect

Tracking

()

Future

People

(Reporter: dbaron, Unassigned)

References

Details

In many parts of the widget code there are platform-specific contract IDs. That doesn't make much sense, since they can't be used. As I understand it, the point of contract IDs is to allow for multiple implementations to be swapped in, whereas each implementation should have a unique CID, or something like that. I'm not against GFX having the same CID for multiple implementations since CIDs are probably more efficient. But anyway, the bigger problem is that we have tons of contract IDs all over the widget factories that are useless. We also have some that have been commented out in the GFX factories. And there are also some implementations of timers that use a different CID for timers other than NS_TIMER_CID. This should be cleaned up. I'm assigning the bug to myself, although I don't intend to do it in the near future.
i always wondered about that.
Blocks: 79119, qt
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → Future
A few of these were fixed by bug 211360.
Depends on: 211360
Product: Core → Core Graveyard
We still have the weird platform-specific contractIDs. (Not that we should really even be *using* contract IDs here if things aren't swappable...)
Component: GFX → Widget
Product: Core Graveyard → Core
QA Contact: chrispetersen → general
Assignee: dbaron → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.