Closed Bug 3666 Opened 26 years ago Closed 26 years ago

XUL Fragments aren't doing the merging correctly

Categories

(Core :: XUL, defect, P2)

x86
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: hyatt, Assigned: hyatt)

Details

XUL Fragments need to still have their own data source in the case where they are imported.
Priority: P3 → P2
Target Milestone: M4
setting p2 for m4
Status: NEW → ASSIGNED
Target Milestone: M4 → M5
Pushing off to m5. We don't have persistence yet, so how we do the merging is irrelevant at this point.
Target Milestone: M5 → M6
moving to m6
Moving back to M5.
Target Milestone: M6 → M8
Still pointless. No persistence, and bugs in Gecko make it hard to even use fragments yet. Moving to M8.
Target Milestone: M8 → M9
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Resolved with the obsoleting of fragments in favor of overlays.
Status: RESOLVED → VERIFIED
QA Contact: danm → ckritzer
Changing QA Contact to ckritzer@netscape.com. Marking VERIFIED FIXED (obsoleted) per hyatt's comments.
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: ckritzer → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.