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

Split the cache API into its own spec #879

Open
jakearchibald opened this Issue Apr 12, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@jakearchibald
Copy link
Collaborator

jakearchibald commented Apr 12, 2016

They're separate, so should be separate

@jakearchibald jakearchibald added this to the Version 1 milestone Apr 12, 2016

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Apr 12, 2016

F2F: group agrees

@jakearchibald jakearchibald self-assigned this Apr 12, 2016

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Apr 12, 2016

F2F: decide on this before v1, but leaning towards yes. I'll do the work when I have time.

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 27, 2016

Pre F2F notes: Do we still want this for V1? Where should the new spec live? WICG?

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 28, 2016

F2F:

  • This isn't high priority
  • We should do this when we're making significant changes, eg the transactions stuff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment