Open Bug 112063 Opened 23 years ago Updated 2 years ago

Don't build full-blown XUL elts for failed merges

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Platform:
x86
Windows 2000
Type:
defect

Tracking

()

Milestone:
Future

People

(Reporter: hyatt, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: helpwanted, memory-footprint)

Rather than merging in using a real content model, we should do all overlay merging using prototypes. This has the effect of avoiding remerging in subsequent windows of the same type, as well as avoiding ever building real XUL elements for overlay files. This bug proposes to disable the ability to use overlays for any namespace other than XUL. IMO eventually what we should do is make the XUL content model the XML content model and go forward that way.
This will also make fastloading of XUL simpler, since we can blast out a master prototype document with all elements already merged in.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.7
Changing this bug to cover only building heavyweight XUL elts once you know a merge is going to be successful. This will help reduce the cost of failed merges.
Assignee: hyatt → waterson
Status: ASSIGNED → NEW
Summary: Perform overlay merging at the prototype element level. → Don't build full-blown XUL elts for failed merges
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Blocks: 104400
Status: NEW → ASSIGNED
Keywords: footprint, helpwanted
Priority: -- → P3
Target Milestone: mozilla0.9.8 → Future
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: waterson → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.