remove synchronous document.cookie api to avoid jank; use cookieStore… #11662
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
removing it from the spec right away doesn't sound a good first step of deprecating features to me. I see it's a major source of jank, but it's still implemented across browsers and implementations need a spec to refer to. |
|
Okay, I see. I will try to create issues to Chromium, Gecko and Webkit to suggest mark this synchronous document.cookie api as deprecated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #11658, synchronous document.cookie API calls are a major source of jank, and the asynchronous CookieStore API can be used as a replacement. Therefore, document.cookie should be removed from the WHATWG HTML Specification to prevent its widespread use in web pages.
/browsers.html ( diff )
/dom.html ( diff )