summaryrefslogtreecommitdiffstats
path: root/dom/base
Commit message (Collapse)AuthorAgeLines
* Issue #1395 - Remove FlyWeb ServiceMatt A. Tobin2020-02-06-50/+0
|
* Issue #1390 - Get rid of the Presentation APIMatt A. Tobin2020-02-06-26/+0
|
* Issue #1384 - Match standard for colSpan/rowSpanwin7-72020-02-03-1/+51
| | | | | | HTML standardizes proper behavior of colSpan and rowSpan: The main thing is that getting the .rowSpan and .colSpan IDL properties will now return the actual clamped value that we use.
* Bug 1430951 - Avoid element name atomizing to improve performance of ↵Gaming4JC2020-01-26-9/+12
| | | | | | | | 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-19/+96
| | | | 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-8/+7
| | | | Tag UXP Issue #1344
* Bug 1406922 - Make CycleCollectedJSContext to handle microtasks and make ↵Gaming4JC2020-01-26-42/+81
| | | | | | MutationObserver to use them Tag UXP Issue #1344
* Bug 1405821 - Move microtask handling to CycleCollectedJSContextGaming4JC2020-01-26-78/+18
| | | | Tag UXP Issue #1344
* Bug 1415761 - Catch the exception and rethrow it after invoking custom ↵Gaming4JC2020-01-26-3/+13
| | | | | | | | elements reactions; The spec was unclear on how CEReactions interact with thrown exceptions; see https://github.com/whatwg/html/issues/3217. The spec is now being clarified in https://github.com/whatwg/html/pull/3235. Tag UXP Issue #1344
* Bug 1396620 - Part 2: Fix compartment mismatch crash when doing old ↵Gaming4JC2020-01-26-0/+4
| | | | | | prototype swizzling for custom element Tag UXP Issue #1344
* Bug 1396620 - Part 1: Remove created callback for custom elementsGaming4JC2020-01-26-98/+22
| | | | Tag UXP Issue #1344
* Bug 1400762 - Make dom.webcomponents.enabled pref doesn't control ↵Gaming4JC2020-01-26-3/+2
| | | | | | 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-14/+121
| | | | Tag UXP Issue #1344
* Bug 1406325 - Part 4: Use mType for LookupCustomElementDefinition and also ↵Gaming4JC2020-01-26-106/+25
| | | | | | removing parts of v0. Tag UXP Issue #1344
* Bug 1406325 - Part 3: Refactor custom elements clone a node.Gaming4JC2020-01-26-25/+19
| | | | Tag UXP Issue #1344
* Bug 1406325 - Part 2: Set CustomElementData when cloning a node.Gaming4JC2020-01-26-4/+4
| | | | Tag UXP Issue #1344
* Bug 1406325 - Part 1: Make sure custom element state is custom before ↵Gaming4JC2020-01-26-5/+14
| | | | | | sending callback. Tag UXP Issue #1344
* Bug 1378079 - Part 3: Complete the steps related to custom elements in ↵Gaming4JC2020-01-26-2/+8
| | | | | | | | "create an element for a token". With fixup for missing header due to unified builds. Tag UXP Issue #1344
* Bug 1378079 - Part 2: Introduce throw-on-dynamic-markup-insertion counter.Gaming4JC2020-01-26-1/+40
| | | | | | Per spec, document objects have a throw-on-dynamic-markup-insertion counter, which is used in conjunction with the create an element for the token algorithm to prevent custom element constructors from being able to use document.open(), document.close(), and document.write() when they are invoked by the parser. Tag UXP Issue #1344
* Bug 1410790 - Add more assertion in ↵Gaming4JC2020-01-26-31/+52
| | | | | | | | 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/+15
| | | | | | ensure upgrade reactions aren't scheduled to BackupQueue; Tag UXP Issue #1344
* Bug 1407937 - Move mDefinition from CustomElementReacion to ↵Gaming4JC2020-01-26-19/+7
| | | | | | CustomElementUpgradeReaction; Tag UXP Issue #1344
* Bug 1406297 - Fix Document.createElement must report an exception.Gaming4JC2020-01-26-3/+1
| | | | Tag UXP Issue #1344
* Bug 1319342 - Clone a node should enqueue an upgrade reaction.Gaming4JC2020-01-26-5/+23
| | | | Tag UXP Issue #1344
* Bug 1121994 - Implement adopted callback for custom elements.Gaming4JC2020-01-26-11/+73
| | | | Tag UXP Issue #1344
* Bug 1334044: Replace detached callback (v0) with disconnected callback (v1).Gaming4JC2020-01-26-20/+26
| | | | Tag UXP Issue #1344
* Bug 1334043 - Part 2: Make nsContentUtils::EnqueueLifecycleCallback static.Gaming4JC2020-01-26-75/+41
| | | | | | 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-23/+25
| | | | | | (v1). Tag UXP Issue #1344
* Bug 1392970 - Part 2: Get CustomElementDefinition from CustomElementData ↵Gaming4JC2020-01-26-46/+26
| | | | | | when possible. Tag UXP Issue #1344
* Bug 1392970 - Part 1: Make CustomElementDefinition ref-counted and put it in ↵Gaming4JC2020-01-26-50/+139
| | | | | | CustomElementData. Tag UXP Issue #1344
* Bug 1301024 - Part 2: Implement create an element steps.Gaming4JC2020-01-26-5/+34
| | | | Tag UXP Issue #1344
* Bug 1301024 - Part 1: Set CreateElement/CreateElementNS is attribute.Gaming4JC2020-01-26-0/+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-43/+194
| | | | | | | | | | | | | | 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-3/+11
| | | | | | | 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-35/+177
| | | | Tag UXP Issue #1344
* Bug 1299363 - Part 5-1: Make the constructor created by ↵Gaming4JC2020-01-26-43/+54
| | | | | | | | 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-14/+18
| | | | | | | | 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-5/+3
| | | | Tag UXP Issue #1344
* Bug 1299363 - Part 1: Implement construction stack.Gaming4JC2020-01-26-2/+4
| | | | Tag UXP Issue #1344
* Bug 1315885 - Part 4: Implement callback reaction for custom element reactions.Gaming4JC2020-01-26-134/+99
| | | | | | 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 1377993 - Make node slots less memory hungry in common cases.Gaming4JC2020-01-26-118/+188
| | | | Tag UXP Issue #1344
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-02 12:20:13 +0000