Hitchhiker’s Guide Web Standards
•
0 likes•49 views
A talk about getting involved in standards and contributing to the web platform. Discusses to navigate through web specifications and contribute to the platform!
Recommended
More Related Content
Similar to Hitchhiker’s Guide Web Standards
Similar to Hitchhiker’s Guide Web Standards (20)
Recently uploaded
Recently uploaded (20)
Hitchhiker’s Guide Web Standards
- 1. Hitchhiker’s Guide to Web Standards
- 2. Dominic Farolino • twitter.com/domfarolino • github.com/domfarolino • dom@chromium.org • Senior @ University of Cincinnati • Previously Microsoft, Mozilla • Incoming @ Google • Chromium Committer • WHATWG Editor
- 3. What is this talk? @domfarolino dom@chromium.org
- 4. Background & History (this could really be its own talk) @domfarolino dom@chromium.org
- 5. Intro to technical bits of specs @domfarolino dom@chromium.org
- 6. How to get involved? (you can do it!!) @domfarolino dom@chromium.org
- 7. What is a “standard”? Depends on the context @domfarolino dom@chromium.org
- 8. –yours truly “A document specifying observable effects of tech with multiple independent implementations” @domfarolino dom@chromium.org
- 9. –yours truly “A document specifying observable effects of tech with multiple independent implementations” @domfarolino dom@chromium.org
- 11. Unix OS’s Web Tech @domfarolino dom@chromium.org
- 12. Unix OS’s Web Tech HTTP @domfarolino dom@chromium.org
- 13. Unix OS’s Web Tech HTTP JS @domfarolino dom@chromium.org
- 14. Unix OS’s Web Tech HTTP JS Web Platform APIs @domfarolino dom@chromium.org
- 15. Unix OS’s Web Tech HTTP JS Web Platform APIs @domfarolino dom@chromium.org
- 16. Unix OS’s Web Tech HTTP JS Web Platform APIs @domfarolino dom@chromium.org
- 17. Unix OS’s Web Tech HTTP JS Web Platform APIs @domfarolino dom@chromium.org
- 18. Unix OS’s Web Tech HTTP JS Web Platform APIs @domfarolino dom@chromium.org
- 19. Where do Web APIs come from? @domfarolino dom@chromium.org
- 20. const logicalAnswer = “JavaScript” @domfarolino dom@chromium.org
- 23. What is JavaScript • Just a language • History • Standardized by ECMAScript • Multiple independent implementations exist @domfarolino dom@chromium.org
- 24. ES Engines • V8 (Chrome) • Chakra (Edge) • SpiderMonkey (Firefox) • JavaScriptCore (Safari/WebKit) @domfarolino dom@chromium.org
- 28. ECMAScript • Needed to be a general standard @domfarolino dom@chromium.org
- 29. ECMAScript • Needed to be a general standard • Specifies only a language; separation of concerns • Syntax, semantics, constructs, primitives • Language should not know about its environment at all • No explicit knowledge of language’s host (DOM / fetch() / etc) @domfarolino dom@chromium.org
- 30. Web API Origins • Not part of the language itself • Effectively “mixins”, baked into UAs like browsers • Browsers “support” implementations of these standards @domfarolino dom@chromium.org
- 31. Web Standards Bodies @domfarolino dom@chromium.org
- 33. WHATWG • Web Hypertext Application Technology Working Group @domfarolino dom@chromium.org
- 34. WHATWG • Web Hypertext Application Technology Working Group • Formed in 2004 @domfarolino dom@chromium.org
- 35. WHATWG • Web Hypertext Application Technology Working Group • Formed in 2004 • Canonical standards: • HTML • DOM • Fetch • Streams @domfarolino dom@chromium.org
- 37. ES Array, WeakMap, Date
- 38. ES DOM APIs Array, WeakMap, Date document.querySelector
- 39. ES DOM APIs Fetch/Networking Array, WeakMap, Date document.querySelector fetch(), Request(), …
- 40. ES DOM APIs Fetch/Networking Console Array, WeakMap, Date document.querySelector fetch(), Request(), … console.{log, count, …}
- 41. Anatomy of a standard @domfarolino dom@chromium.org
- 45. Look and Feel @domfarolino dom@chromium.org
- 49. JS Type (Object, String, Number, Symbol, Boolean) Web Developer Web IDL Conversion
- 50. Web IDL Sheriff JS Type (Object, String, Number, Symbol, Boolean) Web Developer Web IDL Web IDL Conversion
- 51. Successful callWeb IDL Sheriff JS Type (Object, String, Number, Symbol, Boolean) Algorithm Web Developer Web IDL Web IDL Conversion
- 52. Code Jail Web Developer Web IDL Sheriff JS Type (Object, String, Number, Symbol, Boolean) TypeErrorWeb IDL Web IDL Conversion
- 55. Why use Web IDL? @domfarolino dom@chromium.org
- 56. Why use Web IDL? • Abstraction over ECMAScript text @domfarolino dom@chromium.org
- 57. Why use Web IDL? • Abstraction over ECMAScript text • Takes care of things for us: • Property init (Prototype chain, property descriptors, …) • Type conversion • Where to expose interfaces @domfarolino dom@chromium.org
- 58. Why use Web IDL? • Abstraction over ECMAScript text • Takes care of things for us: • Property init (Prototype chain, property descriptors, …) • Type conversion • Where to expose interfaces • Don’t have to use it @domfarolino dom@chromium.org
- 59. How I got involved? @domfarolino dom@chromium.org
- 66. Things I’ve done
- 67. Things I’ve done • Changed how fetch() works
- 68. Things I’ve done • Changed how fetch() works • Changed how module scripts are fetched
- 69. Things I’ve done • Changed how fetch() works • Changed how module scripts are fetched • <script referrerpolicy=“”>
- 70. Things I’ve done • Changed how fetch() works • Changed how module scripts are fetched • <script referrerpolicy=“”> • Implemented console APIs
- 71. Things I’ve done • Changed how fetch() works • Changed how module scripts are fetched • <script referrerpolicy=“”> • Implemented console APIs • Priority Hints