Closed Bug 313671 Opened 19 years ago Closed 16 years ago

Can't search for certain characters ('<', '>', quotes) anymore (->SetCookie, attributes, string literals)

Categories

(Webtools Graveyard :: MXR, defect)

Product:
Webtools Graveyard
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: Biesinger, Assigned: justdave)

References

(
URL
)

Details

(Keywords: regression) 

I can't search for callers of SetCookie anymore. This is a common use case of lxr's text search for me, and thus incredibly annoying.
Not being able to search for lesser than, greater than, and any kinds of quotes makes LXR a lot less useful. Searching for specific tags or attributes, for example, is now often impossible.
Regression from bug 311765?
->justdave
Assignee: chase → justdave
(In reply to comment #2)
> Regression from bug 311765?

Yes.  This problem is the reason the patch that's there hasn't been checked in yet and the reason that bug is still open.
*** Bug 314421 has been marked as a duplicate of this bug. ***
This bug prevents both me and bz from fixing certain bugs.
Severity: critical → blocker
Keywords: regression
OS: Linux → All
Hardware: PC → All
Summary: Can't search for ->SetCookie anymore → Can't search for certain characters ('<', '>', quotes) anymore (->SetCookie, attributes, string literals)
we're sorry...
http://weblogs.mozillazine.org/bz/archives/009293.html

Says these things will work if you double-escape things. Is this a fix, or would this mean the fix in bug 311765 (which I can't see, so I have no clue whatsoever) can be worked around, ie, lxr is still vulnerable (to whatever the problem is).

Apologies if the above made little sense, talking about bugs and patches you can't see is confusing.
*** Bug 328087 has been marked as a duplicate of this bug. ***
QA Contact: timeless → lxr
Works correctly on MXR now.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.