Add WPTs for not dispatching cookiechange event when setting already-expired cookie #51527
Conversation
…expired cookie Already expired cookies should not cause cookiechange events to be dispatched. This CL adds tests to verify this for HTTP cookies, document.cookie, and the CookieStore API. This CL only covers cookiechange events being not dispatched to listeners in the DOM, I will add tests for service workers in a separate CL. Bug: 405165851 Change-Id: I023ca8cceb527228951382a1400a18d3dd7218e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6378643 Reviewed-by: Chris Fredrickson <[email protected]> Commit-Queue: Dylan Cutler <[email protected]> Cr-Commit-Position: refs/heads/main@{#1436296}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-6378643
branch
from
e4333ce to
2707b8b
Compare
|
WPT Command: Some affected tests had inconsistent (flaky) results: Unstable results
These may be pre-existing or new flakes. Please try to reproduce (see the above WPT command, though some flags may not be needed when running locally) and determine if your change introduced the flake. If you are unable to reproduce the problem, please tag |
|
Left a comment (https://crbug.com/405165851#comment3). Please force merge @jcscottiii or @KyleJu. Thanks! |
Already expired cookies should not cause cookiechange events to be
dispatched. This CL adds tests to verify this for HTTP cookies,
document.cookie, and the CookieStore API.
This CL only covers cookiechange events being not dispatched to
listeners in the DOM, I will add tests for service workers in a
separate CL.
Bug: 405165851
Change-Id: I023ca8cceb527228951382a1400a18d3dd7218e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6378643
Reviewed-by: Chris Fredrickson <[email protected]>
Commit-Queue: Dylan Cutler <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1436296}