Closed Bug 127071 Opened 24 years ago Closed 16 years ago

Remove AREA and MAP specific code from parser

Categories

(Core :: DOM: HTML Parser, defect, P5)

defect

Tracking

()

RESOLVED FIXED
Future

People

(Reporter: fabian, Assigned: fabian)

References

Details

(Keywords: memory-footprint)

Attachments

(1 file)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204 BuildID: 20020221 We used to do some special magic to AREA's and MAP's in the parser when building the content model, but that time is over. Gotta remove HTMLContentSink::ProcessMAPTag, HTMLContentSink::ProcessAREATag, nsIHTMLContentSink::OpenMap, nsIHTMLContentSink::CloseMap. The patch still needs some cleanup, but I'll attach it soon enough. Targetting for 1.0 even though I doubt the drivers will like it. Reproducible: Always Steps to Reproduce: 1. Open nsHTMLContentSink.cpp 2. Wonder why there is AREA and MAP specific code 3. Actual Results: Bleh Expected Results: Blah nsHTMLContentSink.cpp needs a spanking. Thus spoke Zaratustra.
Status: NEW → ASSIGNED
Priority: -- → P5
Target Milestone: --- → mozilla1.0
This should do it. Tested and image maps still work fine. HOWEVER I have no idea how to test the other sinks, nsLoggingSink, nsRobotSink, and nsHTMLNullSink. I'd really like an approval from harishd before I even consider checking this in.
nsLoggingSink is used for regression testing. I've never used nsHTMLNullSink/nsRobotSink. Anyway, before I review your patch let me make sure that it doesn't break regression testing.
Cleanup, non-critical -> Post 1.0 job. Waiting for harish's regression tests results, but we're not in a hurry :-)
Target Milestone: mozilla1.0 → mozilla1.1alpha
Future, unless someone updates the patch (I have no idea if it's still needed)
Target Milestone: mozilla1.1alpha → Future
Comment on attachment 70974 [details] [diff] [review] Off with their head. Harish? I really like the number of minuses in this patch and we still seem to have those methods ...
Attachment #70974 - Flags: review?(harishd)
Fabian, have you tested nested MAPs? I'm asking this question because the NavDTD uses a counter ( mOpenMapCount ) to make sure that nested MAPs work correctly and I'm a bit concerned that your patch might break that.
That's a good point I've not tested nested maps I didn't even know it was possible :-) Anyway I am currently unable to do any work on Mozilla (no computer) so feel free to drive the patch into the tree if you really want it :-)
Keywords: footprint
Comment on attachment 70974 [details] [diff] [review] Off with their head. We need to make sure that nested MAPs don't break.
Attachment #70974 - Flags: review?(harishd) → review-
peterv, care to pick this up?
QA Contact: moied → parser
Depends on: 563890
Fixed by Bug 312592 - Reduce content creation redundancy in nsHTMLContentSink Bug 311785 - Simplify nsIHTMLContentSink in late 2005.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: