PushMessageData strings should not be normalized before encoding

Spec doesn't require NFC normalization, and it's considered
bad practice on the Web to muck with user data this way.

BUG=545675
R=peter@chromium.org,jshin@chromium.org,mvanouwerkerk@chromium.org

Review URL: https://codereview.chromium.org/1417773003

Cr-Commit-Position: refs/heads/master@{#355410}

third_party/WebKit/LayoutTests/http/tests/push_messaging/resources/pushmessagedata-worker.js

@@ -125,3 +125,10 @@ test(function() {
     assert_throws(null, () => new PushMessageData(new ArrayBuffer(8)));
 
 }, 'PushMessageData should not be constructable.');
+
+test(function() {
+    var s = "e\u0328"; // 'e' + COMBINING OGONEK
+    var data = createPushMessageData(s);
+    assert_equals(data.text(), s, 'String should not be NFC-normalized.');
+
+}, 'PushEventInit data is not normalized');

third_party/WebKit/Source/modules/push_messaging/PushMessageData.cpp

@@ -33,7 +33,7 @@ PushMessageData* PushMessageData::create(const ArrayBufferOrArrayBufferViewOrUSV
     }
 
     if (messageData.isUSVString()) {
-        CString encodedString = UTF8Encoding().normalizeAndEncode(messageData.getAsUSVString(), WTF::EntitiesForUnencodables);
+        CString encodedString = UTF8Encoding().encode(messageData.getAsUSVString(), WTF::EntitiesForUnencodables);
         return new PushMessageData(encodedString.data(), encodedString.length());
     }