Outdated comments in CNavDTD?

RESOLVED INVALID

Status

()

Core
HTML: Parser
RESOLVED INVALID
17 years ago
13 years ago

People

(Reporter: rbs, Assigned: harishd)

Tracking

Trunk
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
The following code-section seems to suggest that something was planned after
the release of 6.0. However 6.0 has been out for quite some time and no action 
has been taken w.r.t. this. A follow-up is pending here...

> CNavDTD::HandleStartToken()
> ...
> #if 0
>         //we'll move to this approach after beta...
>       if(!isTokenHandled) {
>
>         if(theHeadIsParent && (theExclusive || mOpenHeadCount>0)) {
>           result=AddHeadLeaf(theNode);
>         }
>         else result=HandleDefaultStartToken(aToken,theChildTag,theNode);
>       }
> #else
(Assignee)

Updated

17 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0

Updated

16 years ago
QA Contact: bsharma → moied

Comment 1

16 years ago
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
(Assignee)

Comment 2

16 years ago
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: mozilla1.0.1 → Future

Comment 3

16 years ago
There are a lot of outdated comments in parser code,
I think this is an bug request for clean code.
but it is not important for mozilla 1.0.

I'm going to mark this (very old) bug as INVALID because the code in question
has been changed to reflect the comment (and has evolved even since then). So
this bug is definately RESOLVED, if anyone disagrees with INVALID, feel free to
give it a new resolution.
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.