| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
This was added as part of the WebExtension sec issue CVE-2017-5389.
Since we no longer have this interface, it needed to be removed to
prevent errors in the WebRequest channel callback.
|
|\
| |
| |
| | |
form-disabled-issue
|
| |
| |
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
when the attribute value is an empty string;
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
the constructor.
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
even if some of elements are already unlinked
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
MutationObserver to use them
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
non-custom element
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
prototype swizzling for custom element
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
CustomElements feature
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
validation checks
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
removing parts of v0.
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
sending callback.
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| |
| |
| | |
"create an element for a token".
With fixup for missing header due to unified builds.
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
This is all the manual work for Bug 483155, minus the added functionality to disable SVG and MathML which can be done at any time and are out of scope.
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
ensure upgrade reactions aren't scheduled to BackupQueue;
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
CustomElementUpgradeReaction;
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
(v1).
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
when possible.
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
CustomElementData.
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 mcp-graveyard/UXP%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 mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| | |
Tag UXP Issue mcp-graveyard/UXP%1344
|
| |
| |
| |
| |
| |
| | |
Note: Skipped SyncInvokeReactions since it is removed in CE v1, waste of time.
Tag UXP Issue mcp-graveyard/UXP%1344
|