HTML.next

Cambridge, MA

Woods meeting 2014

Making HTML more agile

  • W3C Process is being revised to improve agility
  • HTML Working Group has a new Work Mode, to match the Web Applications Working Group mode of operations
  • public-html@w3.org is open to everyone
  • Faster release of HTML Recommendations: HTML 5.1 in Q42015?

Extensions specifications

  • Encouraging new ideas through extensions
  • Image description, Media Source, EME, JSON form, Form HTTP, (responsive images), 2D Context, (main, ruby)
  • Other W3C Working Groups are also extending HTML: Web Performance, Web Applications Security, Device API/WebRTC, I18n Tag Set, Web Applications, WAI Protocol and Formats
  • See also Extensions specifications wiki

Future enhancements

  • Continue to push innovation through extensions, with possible reintegration later on (e.g. Resource Priorities, Responsive Images)
  • Continue the integration of Web Components (HTML Imports)
  • Rich Editing
  • Better frames and forms
  • Continue improving HTML accessibility
  • Better integration of HTML and ES6 (including Promises)

Extensions

  • Responsive Design:
    • Image adaptation: <img srcset and <picture>(*)
    • Network congestion: <img lazyload>
    • Baidu submission: First Screen Paint In Advance
  • Accessibility:
    • Image Description: <img longdesc
  • HTTP forms:
    • JSON submission: <form enctype='application/json'>
  • Media:
    • Streaming: mediaBuffer.appendStream(stream)
    • Protection: video.setMediaKeys(key)
  • Security:
    • Content Integrity: <script integrity="ni:///sha-256

Extensible Web
Web Components

Define interactive widgets with ease of composition and reuse

  • Templates: define chunks of markup that are inert but can be activated by script
  • Custom Elements: define elements, with new tag names and new script interfaces.
  • Shadow DOM: Encapsulates DOM subtrees for more reliable composition
  • Imports: defines how templates and custom elements are packaged and loaded

Rich Editing

  • Editing on the Web is a "bloody effing nightmare"
  • Diverse tools and approach: wikis, markdowns, etc.
  • HTML5 contentEditable feature is too high level
  • Interest is growing in solving the issue: Microsoft, Apple, Google, Mozilla
  • Approach:
    • Core enablling function as low level standards
    • Allow rich authoring tools to be developed on top
    • Need to ensure that accessibility and internationalization are addressed (coordination with IndieUI)

Better sandboxes frames
for advertizers

  • Enhancement to allow finer controls, i.e., ability to restrict
    • Individual plugins (Sandbox)
    • Allow / Deny access to a given IFRAME via JavaScript
    • Downloads
    • Alternate navigation

HTML Accessibility

  • ARIA 1.1
  • Full transcript
  • Media Descriptions
  • Date UI widgets
  • Input type numeric
  • …

See HTML 5.1 wishlist

Conclusion

  • There is room for innovation in the HTML markup (e.g. picture)
  • At the end of the day, individuals are doing the work
  • Our Working Group needs to help the HTML community