Closed
Bug 55394
Opened 24 years ago
Closed 13 years ago
Parser and Serializer should have names that indicate what data goes *in*
Categories
(Core :: XML, enhancement, P3)
Core
XML
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: taras.tielkes, Assigned: hjtoi-bugzilla)
References
Details
(Whiteboard: [Replace with DOM 3 Load & Save])
The serializer and parser components of the xmlextras module have names that are a little illocical, in my opinion. The current names (when invoked from ECMAScript) are: -DOMParser -XMLSerializer I think it a better idea to use the object names to indicate what data the object works on, as in: -XMLParser (parses XML) -DOMSerializer (serializes a DOM)
That's right. The changes will reflect better what is happening, and will suggest, e.g., that a DOMSerializer can fan-out to different options/formats.
Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → mozilla0.9
Assignee | ||
Comment 2•24 years ago
|
||
I am taking all XMLExtras bugs to make it easier to see what I am working on...
Assignee: vidur → heikki
Assignee | ||
Comment 3•24 years ago
|
||
Well, DOMSerializer has been there for a while. XMLParser to go.
Assignee | ||
Comment 4•23 years ago
|
||
The DOM Level 3 Load & Save module has DOMBuilder (parser) and DOMWriter (serializer). So to follow that lead we should maybe have DOMParser and DOMSerializer. The better option is to just replace our stuff with DOM 3 stuff.
Assignee | ||
Updated•23 years ago
|
Whiteboard: [Replace with DOM 3 Load & Save]
Assignee | ||
Comment 5•23 years ago
|
||
I do not want to change these so close to the milestone deadline. Besides, I want to replace the DOMParser and XMLSerializer with DOM 3 Load & Save. Moving to 0.9.1 for now.
Target Milestone: mozilla0.9 → mozilla0.9.1
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Nominating for mozilla0.9.2 - mozilla0.9.3. I tried putting "mozilla0.9.2, mozilla0.9.3" but bugzilla rejects mozilla0.9.3, saying it isn't valid keyword.
Keywords: mozilla0.9.2
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Comment 7•23 years ago
|
||
Doesn't look like this is getting fixed before the freeze tomorrow night. Pushing out a milestone. Please correct if I'm mistaken.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.6 → mozilla0.9.8
Assignee | ||
Comment 8•23 years ago
|
||
Well, for better or worse we shipped with the existing names. We could of course introduce new objects and retain the old, but I think I'd prefer just waiting for DOM 3 Load & Save. Moving to Future in the meanwhile. (And btw, I think IBM has something called DOMParser that does basically what we do.)
Target Milestone: mozilla0.9.8 → Future
Updated•22 years ago
|
QA Contact: petersen → rakeshmishra
Updated•21 years ago
|
QA Contact: rakeshmishra → ashishbhatt
Updated•15 years ago
|
QA Contact: ashshbhatt → xml
Comment 9•13 years ago
|
||
The naming ship has sailed so long ago that I think it's safe for me to mark this WONTFIX.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•