| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is in the observed attribute list.
We call attributeChangedCallback in two cases:
1. When any of the attributes in the observed attribute list has changed, appended, removed, or replaced.
2. When upgrading an element, for each attribute in element's attribute list that is in the observed attribute list.
Note: w/ Fixup for not implementing an API Enhancement Bug 1363481.
Tag UXP Issue #1344
|
|
|
|
|
|
|
| |
Per spec [1], we should include namesapce in attributeChangedCallback argurment list.
[1] https://html.spec.whatwg.org/multipage/custom-elements.html#concept-upgrade-an-element, step 3
Tag UXP Issue #1344
|
|
|
|
| |
Tag UXP Issue #1344
|
|
|
|
|
|
|
|
| |
1. It is possible that invoking a reaction triggers pushing a new ElementQueue into ReactionStack (e.g., calling define() in constructor which probably enqueue another upgrade reaction), and the reference of ElementQueue passed to InvokeReactions becomes invalid due to the memmove in nsTArray implementation.
2. And we get another benefit from this is memmove becomes faster.
Tag UXP Issue #1344
|
|
|
|
| |
Tag UXP Issue #1344
|
|
|
|
| |
Tag UXP Issue #1344
|
|
|
|
|
|
| |
Note: Skipped SyncInvokeReactions since it is removed in CE v1, waste of time.
Tag UXP Issue #1344
|
|
|
|
|
|
|
|
| |
of using a map;
Bug 1347446 makes accessing ElementReactionQueue becomes a bit non-trival (have to get it via DocGroup). Since bug 1359346 already refactors the creation time of CustomElementData, ReactionQueue can also be put into CustomElementData, then we can just get ReactionQueue from Element.
Tag UXP Issue #1344
|
|
|
|
|
|
| |
https://dom.spec.whatwg.org/#concept-element-custom-element-state
Tag UXP Issue #1344
|
|
|
|
|
|
| |
code.
Tag UXP Issue #1344
|
|
|
|
| |
Tag UXP Issue #1344
|
|
|
|
|
|
| |
CustomElementRegistry;
Tag UXP Issue #1344
|
|
|
|
| |
Tag UXP Issue #1344
|
|
|
|
|
|
| |
for custom elements;
Tag UXP Issue #1344
|
|
|
|
|
|
| |
a key;
Tag UXP Issue #1344
|
|
|