-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Move event-firing into Storage interface instead of action at a distance #3210
Labels
Comments
annevk
added a commit
that referenced
this issue
May 18, 2020
annevk
added a commit
that referenced
this issue
May 18, 2020
annevk
added a commit
that referenced
this issue
Jun 5, 2020
annevk
added a commit
that referenced
this issue
Jul 8, 2020
annevk
added a commit
that referenced
this issue
Jul 10, 2020
mfreed7
pushed a commit
to mfreed7/html
that referenced
this issue
Sep 11, 2020
Use the new primitives in the Storage Standard. Closes whatwg#3209, closes whatwg#3210, closes whatwg#3283, closes whatwg#4650, closes whatwg#5463, and closes whatwg#5498.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the firing of storage events is done at a distance, via these paragraphs:
These should move into the algorithms for setItem/removeItem/clear, and use actual if statements, and so on.
Formalizing this probably requires some kind of mapping back from storage areas to Storage instances.
The text was updated successfully, but these errors were encountered: