6294 2005-12-29 19:27:36 -0800 DOMString should assert when passed non-ascii characters 2006-11-06 03:37:32 -0800 1 1 1 Unclassified WebKit Platform 420+ Mac OS X 10.4 RESOLVED INVALID P4 Normal --- 6228 1 eric webkit-unassigned ap oldest_to_newest 27199 0 eric 2005-12-29 19:27:36 -0800 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. 47063 1 ap 2006-06-24 15:55:45 -0700 FWIW, I don't see the problem in StringImpl::init() - was it fixed, or am I overlooking it? 46849 2 ap 2006-11-06 03:37:32 -0800 I still don't see the problem, closing as invalid.