Skip to content
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

Observable API #22

Closed
domfarolino opened this issue Aug 14, 2024 · 2 comments
Closed

Observable API #22

domfarolino opened this issue Aug 14, 2024 · 2 comments
Labels
session Breakout session proposal

Comments

@domfarolino
Copy link
Member

domfarolino commented Aug 14, 2024

Session description

In this session we'd like to discuss the Observable API that has been under construction for about a year: https://github.com/WICG/observable. The Chromium implementation is about complete, and the WebKit implementation is very much underway. We'd like to get feedback from folks and move this API to WHATWG stage 3, and hash out any final concerns about integration with the platform.

Session goal

Resolve implementation stances. Move to WHATWG Stage 3

Additional session chairs (Optional)

No response

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

#observable-api

Other sessions where we should avoid scheduling conflicts (Optional)

No response

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

No response

@domfarolino domfarolino added the session Breakout session proposal label Aug 14, 2024
@tpac-breakout-bot
Copy link
Collaborator

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

@domfarolino
Copy link
Member Author

On second thought, this breakout is probably best as a timelsot in the WHATWG session or a WICG-specific session, so I'll close this out.

@domfarolino domfarolino closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal
Projects
None yet
Development

No branches or pull requests

2 participants