Closed Bug 21771 Opened 25 years ago Closed 7 years ago

Factor out code among the HTML/XML/XUL content sinks

Categories

(Core :: DOM: Core & HTML, defect, P2)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: nisheeth_mozilla, Assigned: peterv)

References

Details

(Keywords: arch, highrisk, Whiteboard: [Hixie-P2])

Status: NEW → ASSIGNED
Target Milestone: M14
Accepting and setting milestone to M14 for now...
Blocks: 7516, 7834
Depends on: 7515
No longer depends on: 7515
Blocks: 7515
Blocks: 22176
Bulk moving all M14 non-beta stopper bugs to M17...
Moving bugs out by one milestone...
Target Milestone: M17 → M18
Move back into M17...
Target Milestone: M18 → M17
Move back into M16..
Target Milestone: M17 → M16
Moving XML/HTML content sink factoring related bugs out to M17...
Target Milestone: M16 → M17
This bug has been marked "future" because the original netscape engineer working 
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way 
-- please attach your concern to the bug for reconsideration.
Target Milestone: M17 → Future
No longer blocks: 22176
Nisheeth: Is this going to be one of the first things you implement for 6.1?
Keywords: arch
OS: Windows NT → All
Priority: P3 → P2
Hardware: PC → All
Marking ns6.01 to make sure it is fixed ASAP after the 6.0 release.
Severity: normal → major
Keywords: ns6.01
Keywords: nsbeta1
No longer blocks: 53030
Harish is driving this issue through the mozilla 1.0 time frame.
Assignee: nisheeth → harishd
Status: ASSIGNED → NEW
Target Milestone: Future → ---
harishd: once heikki finishes with bug 43142, I'll be moving the XUL content
model code into the new `content.dll'. This should make factoring the content
sinks much easier.
adding mozilla0.9 keyword since I think this is a big showstopper for xslt and 
we want some time to test transfromiix before final 1.0 release.
Keywords: mozilla0.9
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.1
Futuring for now, might become invalid if and when we get the SAX processing model.
Keywords: nsbeta1 → nsbeta1-
Target Milestone: mozilla0.9.1 → Future
No longer blocks: 53030
Whiteboard: [Hixie-P2]
It seems very odd that arch, highrisk, mozilla1.0, nsbeta1- keywords are placed
on a bug which is futured and hasn't been touched for over four months. I didn't
hear anything about the SAX processing model landing. Did this land while I
wasn't looking? Did it obsolete the bug? Is this no longer a problem?
Is this bug dead? Has work on it been dormant for ten months? Is this a WONTFIX?
In any case, does the mozilla1.0 keyword still apply?
Low priority at the moment, not critical for 1.0.
Keywords: mozilla1.0
No longer blocks: 34849
Any news on that one in the meantime?
Blocks: 191033
peterv has actually been working on this, reassigning to make it clear.
Assignee: harishd → peterv
Status: ASSIGNED → NEW
Target Milestone: Future → mozilla1.4alpha
This counts as a big thing, so adding dependency.

Peter, can you give a status update on this?
Blocks: 193275
I'm working on this but this won't be ready for 1.4.
No longer blocks: 193275
Status: NEW → ASSIGNED
Target Milestone: mozilla1.4alpha → mozilla1.5alpha
Based on the comments in bug 69996, and since most bugs mentioned here have long since been fixed, can this bug now be closed?
The XUL content sink is still very standalone. However I'm not sure this bug adds value as is, it'd probably be better to file more specific bugs.
QA Contact: chrispetersen → layout
Target Milestone: mozilla1.5alpha → ---
This bug doesn't seem to involve any Layout code.
Component: Layout → DOM
Given XUL is planned to be removed, closing per comment 22.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.