- fix http://bugs.webkit.org/show_bug.cgi?id=16179 | <rdar://problem/5619399>
authorslewis@apple.com <slewis@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 20 Dec 2007 22:05:15 +0000 (22:05 +0000)
committerslewis@apple.com <slewis@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 20 Dec 2007 22:05:15 +0000 (22:05 +0000)
commit414e9f3540dbe33aaf53b85dedd1e4603ad07b56
treefd3979d91bd2ed87da7efda7560ffdcda32c077e
parent65464176227365991c1cf88364c7a878ff0e330d
 - fix bugs.webkit.org/show_bug.cgi?id=16179 | <rdar://problem/5619399>
          Any attribute name start with a unicode which like #xx00(x could be any hex number[0-9a-f]) will cause HTMLTokenizer parse error
          Actually any unicode characters which great than 255 in attribute name will cause Webkit parse the attribute name wrong. So after comparing
          the same scenario in IE 6/7, FireFox 2/3, Opera, we should treat those characters as part of attribute name.

        * html/HTMLTokenizer.cpp:
        (WebCore::HTMLTokenizer::parseEntity): Handle Unicode Entity Name by using ASCII version of findEntity.
        (WebCore::HTMLTokenizer::parseTag): Let type of ptr match type of cBuffer.
        * html/HTMLTokenizer.h: Change type of cBuffer from char to UChar.

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@28908 268f45cc-cd09-0410-ab3c-d52691b4dbfc
LayoutTests/ChangeLog
LayoutTests/fast/parser/test-unicode-characters-in-attribute-name-expected.txt [new file with mode: 0644]
LayoutTests/fast/parser/test-unicode-characters-in-attribute-name.html [new file with mode: 0644]
WebCore/ChangeLog
WebCore/html/HTMLTokenizer.cpp
WebCore/html/HTMLTokenizer.h
WebKitTools/Scripts/run-iexploder-tests
WebKitTools/Scripts/run-mangleme-tests