Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(26)

Side by Side Diff: LayoutTests/fast/dom/Element/setAttributeNode-case-insensitivity-expected.txt

Issue 22803008: setAttributeNode() does not properly normalize case. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: submitting patch with small name changes. Created 7 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 Test for Bugzilla bug: 90341: createAttribute/setAttributeNode does not properly normalize case.
2 This test verifies that the setAttributeNode() API checks for existing attribute s case-insensitively. Thus the value of an existing attribute with the same name but in a different case should get replaced by the new value specified via the setAttributeNode() method.
3
4 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".
5
6 PASS test.getAttribute('style') is test.getAttribute('STYLE')
7 PASS test.getAttributeNode('style').value is test.getAttributeNode('STYLE').valu e
8 Verifying that attributes with the same name but different namespaces are treate d as unique entities. For the following test two different attribute values shou ld be returned.
9 PASS test.getAttributeNodeNS('ns1', 'newattr').value is 'newattr1'
10 PASS test.getAttributeNodeNS('ns2', 'newattr').value is 'newattr2'
11 Verifying that attributes with same name but different case and having same name spaces are treated as same. In the following test the new attribute should overw rite the value of the existing one.
12 PASS test.getAttributeNodeNS('ns1', 'newattr').value is 'newattr3'
13 PASS successfullyParsed is true
14
15 TEST COMPLETE
16
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698