-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Add initStorageEvent() #4063
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add initStorageEvent() #4063
Conversation
@@ -93990,7 +93990,7 @@ typedef (<span>WindowProxy</span> or <span>MessagePort</span> or <span>ServiceWo | |||
value it was initialized to. It represents, in <span>cross-document messaging</span> and | |||
<span>channel messaging</span>, the <code>MessagePort</code> array being sent.</p> | |||
|
|||
<!-- handwave this one since it's deprecated anyway... let me know if there's interop issues --> | |||
<!-- handwavy, file bugs if there are interop issues --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could use https://dom.spec.whatwg.org/#dom-customevent-initcustomevent as a template, though maybe we should wait until we have internal slots.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://dom.spec.whatwg.org/#dom-customevent-detail isn't an internal slot, so the same pattern could be followed.
I think some analogue to https://dom.spec.whatwg.org/#inner-event-creation-steps might work here, but there aren't that many initFooEvent
and for all practical purposes I think handwaving plus tests will be enough.
I can do some cleanup though, if you have a specific setup you'd like.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'd prefer waiting until we have internal slots, since what initCustomEvent()
does isn't quite right either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All right, this and the tests are ready for review, then. See web-platform-tests/wpt#13368 (comment) for current behavior.
Tests: web-platform-tests/wpt#13368 Fixes #1054.
764e269
to
df9d721
Compare
…orageEvent(), a=testonly Automatic update from web-platform-testsTest initStorageEvent() Follows whatwg/html#4063. -- Consolidate/simplify StorageEvent constructor tests The use of `async_test` was already unnecessary as `dispatchEvent` synchronously invokes listeners, and use of `dispatcEvent` itself is not necessary to test the constructor, so simplify to just `test`s. -- wpt-commits: c4fce5c3c37e30b192a596c4dc779e4192f1bc12, bd5f3403f34f8e83eecbdc172cd330039e12ab86 wpt-pr: 13368
…orageEvent(), a=testonly Automatic update from web-platform-testsTest initStorageEvent() Follows whatwg/html#4063. -- Consolidate/simplify StorageEvent constructor tests The use of `async_test` was already unnecessary as `dispatchEvent` synchronously invokes listeners, and use of `dispatcEvent` itself is not necessary to test the constructor, so simplify to just `test`s. -- wpt-commits: c4fce5c3c37e30b192a596c4dc779e4192f1bc12, bd5f3403f34f8e83eecbdc172cd330039e12ab86 wpt-pr: 13368
initStorageEvent was standardized in whatwg/html#4063. spec: https://html.spec.whatwg.org/multipage/webstorage.html#the-storageevent-interface Bug: 697170 Change-Id: Ie08062686c82c22a068546e74ec89cbebf65afc8 Reviewed-on: https://chromium-review.googlesource.com/c/1411752 Reviewed-by: Joshua Bell <[email protected]> Reviewed-by: Philip Jägenstedt <[email protected]> Commit-Queue: Amos Lim <[email protected]> Cr-Commit-Position: refs/heads/master@{#623013}
…orageEvent(), a=testonly Automatic update from web-platform-testsTest initStorageEvent() Follows whatwg/html#4063. -- Consolidate/simplify StorageEvent constructor tests The use of `async_test` was already unnecessary as `dispatchEvent` synchronously invokes listeners, and use of `dispatcEvent` itself is not necessary to test the constructor, so simplify to just `test`s. -- wpt-commits: c4fce5c3c37e30b192a596c4dc779e4192f1bc12, bd5f3403f34f8e83eecbdc172cd330039e12ab86 wpt-pr: 13368 UltraBlame original commit: e726946c50a836304adcf437ca93290e061e2a71
…orageEvent(), a=testonly Automatic update from web-platform-testsTest initStorageEvent() Follows whatwg/html#4063. -- Consolidate/simplify StorageEvent constructor tests The use of `async_test` was already unnecessary as `dispatchEvent` synchronously invokes listeners, and use of `dispatcEvent` itself is not necessary to test the constructor, so simplify to just `test`s. -- wpt-commits: c4fce5c3c37e30b192a596c4dc779e4192f1bc12, bd5f3403f34f8e83eecbdc172cd330039e12ab86 wpt-pr: 13368 UltraBlame original commit: e726946c50a836304adcf437ca93290e061e2a71
…orageEvent(), a=testonly Automatic update from web-platform-testsTest initStorageEvent() Follows whatwg/html#4063. -- Consolidate/simplify StorageEvent constructor tests The use of `async_test` was already unnecessary as `dispatchEvent` synchronously invokes listeners, and use of `dispatcEvent` itself is not necessary to test the constructor, so simplify to just `test`s. -- wpt-commits: c4fce5c3c37e30b192a596c4dc779e4192f1bc12, bd5f3403f34f8e83eecbdc172cd330039e12ab86 wpt-pr: 13368 UltraBlame original commit: e726946c50a836304adcf437ca93290e061e2a71
…orageEvent(), a=testonly Automatic update from web-platform-testsTest initStorageEvent() Follows whatwg/html#4063. -- Consolidate/simplify StorageEvent constructor tests The use of `async_test` was already unnecessary as `dispatchEvent` synchronously invokes listeners, and use of `dispatcEvent` itself is not necessary to test the constructor, so simplify to just `test`s. -- wpt-commits: c4fce5c3c37e30b192a596c4dc779e4192f1bc12, bd5f3403f34f8e83eecbdc172cd330039e12ab86 wpt-pr: 13368
Tests: web-platform-tests/wpt#13368
Fixes #1054.
/webstorage.html ( diff )