Revision f048355b3d2fd2468e37ddd916b6f0166aad0739 authored by Stephen McGruer on 13 April 2018, 16:52:45 UTC, committed by Chromium WPT Sync on 13 April 2018, 16:52:45 UTC
There were three minor bugs left in the implementation:
- We threw on lists-in-custom-iterators instead of just ignoring them.
- We returned all properties on the keyframe rather than just those
defined on the keyframe itself (e.g. we would include prototype
properties, against spec).
- We didn't access the properties in ascending unicode order.
Bug: 827573
Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88
Reviewed-on: https://chromium-review.googlesource.com/989261
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550641}
1 parent 1e5a5fe
format-leading-space.htm
<!doctype html>
<html>
<head>
<title>EventSource: leading space</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
</head>
<body>
<div id="log"></div>
<script>
var test = async_test()
test.step(function() {
var source = new EventSource("resources/message.py?message=data%3A%09test%0Ddata%3A%20%0Adata%3Atest")
source.onmessage = function(e) {
test.step(function() {
assert_equals("\ttest\n\ntest", e.data)
source.close()
})
test.done()
}
})
</script>
<!-- also used a CR as newline once -->
</body>
</html>
Computing file changes ...
