You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been ramping up various work on getting Firefox closer towards the latest 6265bis draft.
When reviewing the pull request #1732, I noticed that the wpt tests developed alongside are using the CookieStore API that is only supported by Chromium browsers.
Considering previous and ongoing work to improve Cookie APIs in the test infra (web-platform-tests/rfcs#74, web-platform-tests/rfcs#108), may I suggest that we refrain from using the CookieStore API in for new changes and their tests?
The text was updated successfully, but these errors were encountered:
heya @mozfreddyb - can you link to the tests in question? I agree we shouldn't use that API to test cookies, but it would be helpful if you can point to the tests (or file a bug on WPT or Chromium and tag me).
I was under the impression that those were meant to be the accompanying commits to wpt for that cookie spec change. Revisiting the commits, I now understand that this is not the case. That commit merely changes the default expiry behavior for the existing CookieStore API tests. In fact, there are no accompanying commits to wpt for #1732 at all. My apologies.
Hi folks working on 6265bis,
We've been ramping up various work on getting Firefox closer towards the latest 6265bis draft.
When reviewing the pull request #1732, I noticed that the wpt tests developed alongside are using the CookieStore API that is only supported by Chromium browsers.
Considering previous and ongoing work to improve Cookie APIs in the test infra (web-platform-tests/rfcs#74, web-platform-tests/rfcs#108), may I suggest that we refrain from using the CookieStore API in for new changes and their tests?
The text was updated successfully, but these errors were encountered: