Closed
Bug 275288
Opened 20 years ago
Closed 20 years ago
Remove CRC calculations from CNavDTD
Categories
(Core :: DOM: HTML Parser, defect)
Core
DOM: HTML Parser
Tracking
()
RESOLVED
FIXED
People
(Reporter: mrbkap, Assigned: mrbkap)
Details
Attachments
(1 file)
|
9.96 KB,
patch
|
roc
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
Currently, we have #ifdef'd out code in CNavDTD/nsDTDUtils that calculates the CRC32 value of a given document. I don't think anybody since RickG even knows or cares about any CRC values for any documents, so I've taken all of the code out. Patch upcoming shortly.
| Assignee | ||
Comment 1•20 years ago
|
||
This patch may apply with some fuzz (a couple of lines, I hope). It removes the
CRC stuff from the parser.
Note: there is one part where we end up with a construct like:
if (NS_SUCCEEDED(result)) {
if (NS_OK == result) {
...
}
}
I've left this the way it was because the parser does some funky stuff with
return values (just under that it has nsresult result = 1;). If you want me to
take the ifs out, please tell me.
Attachment #169116 -
Flags: superreview?(roc)
Attachment #169116 -
Flags: review?(jst)
Comment on attachment 169116 [details] [diff] [review] patch v1 I'm taking the liberty of giving r+ for this trivial patch...
Attachment #169116 -
Flags: superreview?(roc)
Attachment #169116 -
Flags: superreview+
Attachment #169116 -
Flags: review?(jst)
Attachment #169116 -
Flags: review+
| Assignee | ||
Comment 3•20 years ago
|
||
Checked in.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•