summaryrefslogtreecommitdiffstats
path: root/dom/base/CustomElementRegistry.cpp
Commit message (Collapse)AuthorAgeLines
* Issue #80 - De-unify dom/baseMatt A. Tobin2020-04-17-0/+2
| | | | Tag #1375
* Bug 1417829 - Remove unresolved pseudoclassMatt A. Tobin2020-04-17-3/+0
| | | | Tag #1375
* Bug 1422197 - Add fast path to get DocGroup in binding code for [CEReactions]Matt A. Tobin2020-04-17-0/+6
| | | | Tag #1375
* Bug 1416999 - Remove document.registerElementMatt A. Tobin2020-04-17-16/+3
| | | | Tag #1375
* Issue #1375 - Stop largely using the parser serviceMatt A. Tobin2020-04-17-8/+2
| | | | | | | | | This is based on Bug 1395828 * Add nsHTMLElement::IsBlock() * Rename nsHTMLTags methods * Remove AssertParserServiceIsCorrect() * Remove most uses of nsIParserService/nsParserService
* Bug 1430951 - Avoid element name atomizing to improve performance of ↵Gaming4JC2020-01-26-3/+2
| | | | | | | | LookupCustomElementDefinition Since we are dealing with the element (nodeInfo->LocalName() and NameAtom() are the same value), we could use nodeInfo->NameAtom() instead. Tag UXP Issue #1344
* Bug 1430034 - Fix attributeChangedCallback isn't fired with correct newValue ↵Gaming4JC2020-01-26-1/+1
| | | | | | when the attribute value is an empty string; Tag UXP Issue #1344
* Bug 1421544 - Lazy push/pop CustomElementReactionsStack entry;Gaming4JC2020-01-26-4/+20
| | | | Tag UXP Issue #1344
* Bug 1413815 - Convert 'observedAttributes' to a sequence<DOMString>Gaming4JC2020-01-26-5/+13
| | | | Tag UXP Issue #1344
* Bug 1407669 - Fix custom element creation hides uncatchable exceptions from ↵Gaming4JC2020-01-26-0/+1
| | | | | | the constructor. Tag UXP Issue #1344
* Bug 1419305 - Part 2: Keep processing remaining elements in ElementQueue ↵Gaming4JC2020-01-26-4/+5
| | | | | | even if some of elements are already unlinked Tag UXP Issue #1344
* Bug 1419305 - Part 1: Use MicroTask on CustomElements correctlyGaming4JC2020-01-26-3/+2
| | | | Tag UXP Issue #1344
* Bug 1405821 - Move microtask handling to CycleCollectedJSContextGaming4JC2020-01-26-0/+1
| | | | Tag UXP Issue #1344
* Bug 1396620 - Part 1: Remove created callback for custom elementsGaming4JC2020-01-26-70/+7
| | | | Tag UXP Issue #1344
* Bug 1400762 - Make dom.webcomponents.enabled pref doesn't control ↵Gaming4JC2020-01-26-2/+1
| | | | | | CustomElements feature Tag UXP Issue #1344
* Bug 1405335 - Remove custom element attached and detached callbacks ↵Gaming4JC2020-01-26-3/+1
| | | | | | validation checks Tag UXP Issue #1344
* Bug 1406325 - Part 5: Implement try to upgrade.Gaming4JC2020-01-26-0/+18
| | | | Tag UXP Issue #1344
* Bug 1406325 - Part 4: Use mType for LookupCustomElementDefinition and also ↵Gaming4JC2020-01-26-52/+12
| | | | | | removing parts of v0. Tag UXP Issue #1344
* Bug 1378079 - Part 3: Complete the steps related to custom elements in ↵Gaming4JC2020-01-26-1/+5
| | | | | | | | "create an element for a token". With fixup for missing header due to unified builds. Tag UXP Issue #1344
* Bug 1410790 - Add more assertion in ↵Gaming4JC2020-01-26-0/+42
| | | | | | | | CustomElementData::SetCustomElementDefinition and GetCustomElementDefinition; This is a follow-up patch for bug 1392970. Since we only set CustomElementDefinition on a custom element which is custom, we could add more assertion to ensure that. Tag UXP Issue #1344
* Bug 1352290 - Add assertion to CustomElementReactionsStack::Enqueue to ↵Gaming4JC2020-01-26-0/+2
| | | | | | ensure upgrade reactions aren't scheduled to BackupQueue; Tag UXP Issue #1344
* Bug 1407937 - Move mDefinition from CustomElementReacion to ↵Gaming4JC2020-01-26-5/+2
| | | | | | CustomElementUpgradeReaction; Tag UXP Issue #1344
* Bug 1406297 - Fix Document.createElement must report an exception.Gaming4JC2020-01-26-3/+1
| | | | Tag UXP Issue #1344
* Bug 1121994 - Implement adopted callback for custom elements.Gaming4JC2020-01-26-6/+29
| | | | Tag UXP Issue #1344
* Bug 1334044: Replace detached callback (v0) with disconnected callback (v1).Gaming4JC2020-01-26-12/+16
| | | | Tag UXP Issue #1344
* Bug 1334043 - Part 2: Make nsContentUtils::EnqueueLifecycleCallback static.Gaming4JC2020-01-26-19/+14
| | | | | | We make nsContentUtils::EnqueueLifecycleCallback static so that it can be called without a window object. To achive this, we also make CustomElementReaction not taking a CustomElementRegistry in the constructor, as it can call Upgrade statically. Tag UXP Issue #1344
* Bug 1334043 - Part 1: Replace attached callback (v0) with connected callback ↵Gaming4JC2020-01-26-14/+17
| | | | | | (v1). Tag UXP Issue #1344
* Bug 1392970 - Part 2: Get CustomElementDefinition from CustomElementData ↵Gaming4JC2020-01-26-40/+25
| | | | | | when possible. Tag UXP Issue #1344
* Bug 1392970 - Part 1: Make CustomElementDefinition ref-counted and put it in ↵Gaming4JC2020-01-26-46/+63
| | | | | | CustomElementData. Tag UXP Issue #1344
* Bug 1301024 - Part 2: Implement create an element steps.Gaming4JC2020-01-26-4/+8
| | | | Tag UXP Issue #1344
* Bug 1332233 - prevent resource leak in CustomElementRegistry::Define.Gaming4JC2020-01-26-8/+9
| | | | Tag UXP Issue #1344
* Bug 1334051 - Part 2: Invoke attributeChangedCallback only if attribute name ↵Gaming4JC2020-01-26-11/+108
| | | | | | | | | | | | | | 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
* Bug 1334051 - Part 1: Include namespace in attributeChangedCallback.Gaming4JC2020-01-26-1/+1
| | | | | | | 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
* Bug 1299363 - Part 5-2: Implement new upgrade steps.Gaming4JC2020-01-26-28/+154
| | | | Tag UXP Issue #1344
* Bug 1299363 - Part 5-1: Make the constructor created by ↵Gaming4JC2020-01-26-34/+0
| | | | | | | | document.registerElement() also works with construction stack. So that the old upgrade can also work with new upgrade steps which will be implemented in part 5-2. Tag UXP Issue #1344
* Bug 1353647 - Fix the custom elements v0 upgrade inconsistency;Gaming4JC2020-01-26-15/+25
| | | | | | | | | | | | There are two places doing prototype setup in old upgrade, - If definition comes after JS reflector creation, CustomElementRegistry::Upgrade will do prototype swizzling. - If definition comes before JS reflector creation, Element::WrapObject will set up the prototype. The later one does SubsumesConsideringDomain, but the former doesn't not. This patch is to fix the inconsistency, i.e. the former case should also do SubsumesConsideringDomain. Tag UXP Issue #1344
* Bug 1299363 - Part 4: Hold a pointer of ElementQueue in ReactionsStack instead.Gaming4JC2020-01-26-12/+16
| | | | | | | | 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
* Bug 1299363 - Part 3: Remove unused argument in UpgradeCandidates.Gaming4JC2020-01-26-3/+2
| | | | Tag UXP Issue #1344
* Bug 1315885 - Part 4: Implement callback reaction for custom element reactions.Gaming4JC2020-01-26-105/+55
| | | | | | Note: Skipped SyncInvokeReactions since it is removed in CE v1, waste of time. Tag UXP Issue #1344
* Bug 1315885 - Part 3: Transfer the ownership of ReactionQueue's entry due to ↵Gaming4JC2020-01-26-3/+8
| | | | | | re-enter CustomElementReactionsStack::InvokeReactions. Tag UXP Issue #1344
* Bug 1315885 - Part 2: Avoid rethrowing exception in CustomElementCallback::Call.Gaming4JC2020-01-26-0/+4
| | | | Tag UXP Issue #1344
* Bug 1325279 - Put the reaction queue in CustomElementData structure instead ↵Gaming4JC2020-01-26-17/+12
| | | | | | | | 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
* Bug 1359346 - Implement custom element state;Gaming4JC2020-01-26-22/+28
| | | | | | https://dom.spec.whatwg.org/#concept-element-custom-element-state Tag UXP Issue #1344
* Bug 1357002 - Part 1: Cache dom.webcomponents.customelements.enabled preference;Gaming4JC2020-01-26-1/+1
| | | | Tag UXP Issue #1344
* Bug 1341898 - Make nsDocument::IsWebComponentsEnabled use a cached bool pref;Gaming4JC2020-01-26-1/+1
| | | | | | Note: Minus IPC bit. Tag UXP Issue #1344
* Bug 1309147 - Part 5: Eliminate performance cliff when accessing CEReactions ↵Gaming4JC2020-01-26-2/+9
| | | | | | code. Tag UXP Issue #1344
* Bug 1309147 - Part 4: Add CEReactions for CustomElementRegistry.Gaming4JC2020-01-26-9/+0
| | | | Tag UXP Issue #1344
* Bug 1351979 - Change CustomElementRegistry::Define code to properly ↵Gaming4JC2020-01-26-1/+1
| | | | | | propagate out JS exceptions; Tag UXP Issue #1344
* Bug 1347446 - Move custom element reactions stack to DocGroup.Gaming4JC2020-01-26-20/+38
| | | | Tag UXP Issue #1344
* Bug 1341693 - Don't need to check GetDocShell() when creating ↵Gaming4JC2020-01-26-30/+4
| | | | | | CustomElementRegistry; Tag UXP Issue #1344
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 21:48:34 +0000