RESOLVED FIXED 12884
Test SVG custom parsers 
https://bugs.webkit.org/show_bug.cgi?id=12884
Summary Test SVG custom parsers
Maciej Stachowiak
Reported 2007-02-24 19:08:23 PST
We should do fuzz-testing of SVG parsers to make sure we've adressed possible overflow bugs. Maybe also more code review. This applies to at least the following parsers: - paths - SVGTransformable::parseTransformAttribute - SVGLengthList::parse - SVGNumberList::parse - SVGStringList::parse - SVGPreserveAspectRatio::parsePreserveAspectRatio - SVGColor.cpp parseNumberOrPercent - SVGColor::colorFromRGBColorString - SVGFitToViewBox::parseViewBox - SVGLength::setValueAsString - SVGParserUtilities.cpp parseNumber - SVGParserUtilities.cpp parseNumberOptionalNumber - SVGPolyParser::parsePoints - SVGPathParser::parseSVG - CSSParser::parseSVGStrokeDasharray - CSSParser::parseSVGPaint - CSSParser::parseSVGColor - CSSParser::parseSVGValue Parsers that are only in relevant to experimental features (so testing them isn't a P1): - SVGAnimationElement::parseKeyNumbers - SVGAnimationElement parseValues, parseKeySplines - SVGAnimationElement::parseBeginOrEndValue - SVGAnimationElement::parseClockValue - SVGAnimateMotionElement.cpp parsePoint static function
Attachments
Add attachment proposed patch, testcase, etc.
Maciej Stachowiak
Comment 1 2007-02-24 19:10:38 PST
<rdar://problem/5021699>
Darin Adler
Comment 2 2007-04-11 02:21:36 PDT
Geoff took care of this and closed the Radar bug on 3/21.
Note You need to log in before you can comment on or make changes to this bug.