Skip to content
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.

Implementing W3C and WHATWG specifications on NG #21

Open
lewispham opened this issue Sep 14, 2015 · 5 comments
Open

Implementing W3C and WHATWG specifications on NG #21

lewispham opened this issue Sep 14, 2015 · 5 comments

Comments

@lewispham
Copy link

I think NG should cover some APIs that belong to body standards.
List of proposed APIs:

@ChALkeR
Copy link
Member

ChALkeR commented Sep 14, 2015

Canvas? In core? What for?

@yosuke-furukawa
Copy link
Member

#17 is related.

@yosuke-furukawa
Copy link
Member

I don't think those higher level API should be on core.
Core API should be more stable and lower level.
Higher level APIs should be on userland.

BUT, IMO the following APIs are needed to be discussed that core is better or non-core is better.

  • http2 (we already implemented http. IMHO, we would be better to implement http/2)
  • workers (we have PR, but not landed yet.)
  • console (Browser console is pandora box...)
  • whatwg-url
  • blobs, etc

@lewispham
Copy link
Author

I think listed APIs should be implemented on an extended version, not the core.

@lygstate
Copy link

WebGL

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants