Closed Bug 731162 Opened 12 years ago Closed 12 years ago

Zap nsIParser::Parse(const nsAString&, ...

Categories

(Core :: DOM: HTML Parser, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla14

People

(Reporter: hsivonen, Assigned: hsivonen)

References

Details

Attachments

(1 file, 1 obsolete file)

Remove legacy code when it becomes dead code.
Assignee: nobody → hsivonen
Status: NEW → ASSIGNED
Aargh. nsParser still has internal dependencies on this for XML fragment parsing. Scoping for zapping it from nsIParser only in order to avoid new callers cropping up.
Summary: Zap nsParser::Parse(const nsAString&, ... → Zap nsIParser::Parse(const nsAString&, ...
Oh well. This turned out to be not much of a removal win at this point.
Even though this removal turned out not to be much of a win, I want to remove this method from nsIParser to make sure comm-central or XULRunner apps don't add new calls to it while I'm not paying attention.
Attachment #601232 - Attachment is obsolete: true
Attachment #608240 - Flags: review?(bugs)
how much would it take remove the xml dependencies.
(In reply to Olli Pettay [:smaug] from comment #4)
> how much would it take remove the xml dependencies.

It looked complicated enough not to be worth it before the larger XML code path rewrite. (Check out what the XML code path does. It's quite horrible.)
Attachment #608240 - Flags: review?(bugs) → review+
https://hg.mozilla.org/mozilla-central/rev/902b81504db9
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
Depends on: 798275
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: