Closed Bug 1458116 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 10727 - Cookie Store: Move non-ASCII codepoint test cases to dedicated tests

Categories

(Testing :: web-platform-tests, enhancement, P4)

Product:
Testing
Component:
web-platform-tests
Type:
enhancement

Tracking

(firefox62 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla62
Tracking Flags:
Tracking Status
firefox62 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 10727 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/10727 Details from upstream follow. Joshua Bell <jsbell@chromium.org> wrote: > Cookie Store: Move non-ASCII codepoint test cases to dedicated tests > > Cookie handling of non-ASCII codepoints is not consistent across > browsers, so we definitely want tests that exercise these. To make > potential failures here more obvious, make sure that there are > dedicated test cases for non-ASCII interop with other ways of > getting/setting cookies (HTTP headers, document.cookie). > > Also, make the document.cookie interop tests symmetric: > set/overwrite/delete by CookieStore observed by document.cookie and > vice versa. > > Bug: 729800 > Change-Id: I637401e5f8021a2915ba186fbb1cf7a50e940905 > Reviewed-on: https://chromium-review.googlesource.com/1036306 > WPT-Export-Revision: 75182a141128aaef162fab73eb4cb8f569302def
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Ran 11 tests and 16 subtests OK : 11 FAIL : 16
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/036b1f0a38e6 [wpt PR 10727] - Cookie Store: Move non-ASCII codepoint test cases to dedicated tests, a=testonly
https://hg.mozilla.org/mozilla-central/rev/036b1f0a38e6
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.