RESOLVED INVALID 6294
DOMString should assert when passed non-ascii characters
https://bugs.webkit.org/show_bug.cgi?id=6294
Summary DOMString should assert when passed non-ascii characters
Eric Seidel (no email)
Reported 2005-12-29 19:27:36 PST
Darin's comments on 6228: In parseUASheet, we can make the DOMString from the char* without decoding because we know it has all ASCII characters in it. Unlike QString, that function does not work for non-ASCII Latin-1 characters. So I think it's worth a comment and adding an assertion to DOMStringImpl::DOMStringImpl(const char *) to check for non-ASCII characters.
Attachments
Alexey Proskuryakov
Comment 1 2006-06-24 15:55:45 PDT
FWIW, I don't see the problem in StringImpl::init() - was it fixed, or am I overlooking it?
Alexey Proskuryakov
Comment 2 2006-11-06 03:37:32 PST
I still don't see the problem, closing as invalid.
Note You need to log in before you can comment on or make changes to this bug.