TPE DOM/Custom elements: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 38: Line 38:
#window.customElements.define
#window.customElements.define
#*Bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1275835 1275835]
#*Bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1275835 1275835]
[Stage 2]
[Stage 2] <Target milestone: TBD in 2016 Q4)
#custom element reactions stack/queue
#custom element reactions stack/queue
#*Callback reaction
#*Callback reaction

Revision as of 03:26, 22 July 2016

Introduction

This project is to enable web authors to define and use new types of DOM elements in a document.

References:


Taipei Main Members

Engineers: Edgar Chen, Jocelyn Liu, John Dai

Meeting Minutes

Sync-up minutes

High-level Roadmap

[Stage 1] <We are here - Target milestone: 2016 Q3>

  1. Remove support of SVG-based custom element.
  2. Window interface
  3. HTMLElement constructor
    • Support using ES6 classes
    • Construction stack
    • Bug: 1274159
  4. Document interface
    • createElement, createElementNS
    • Bug: 1276579
  5. window.customElements.define

[Stage 2] <Target milestone: TBD in 2016 Q4)

  1. custom element reactions stack/queue
    • Callback reaction
    • sProcessingStack
    • EnqueueLifecycleCallback
    • Upgrade reaction
  2. Lifecycle callbacks
    • connectedCallback
    • disconnectedCallback
    • attributeChangedCallback
  3. Algorithm of creating an element

[Stage 3]

  1. Mutation algorithms (Shadow dom)
  2. Web-platform-tests

[Stage 4]

  1. CSS :define

Project Dashboard

Meta Bugs

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Ship Bugs (Stage 1)

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1