| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
| |
KeyframeAnimationOptions.
This is a hack to deal UnifiedBindings trying to deal with an incomplete codegen implementation so it was worked around with a hack back in Firefox 30-something. If we have anymore of this non-sense crop up as stuff is added or removed from DOM then extend this conditional.
Least until something better comes along.
|
|\
| |
| | |
Merging this in even without a test performed since the code change looks sane. real-world testing will have to be performed.
|
| |
| |
| |
| | |
It's at ~1.5% on the perf log for the Netflix use case, which seems a bit too much.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
If EME isn't built, these functions would have no use and the callback
structures are unavailable. Stubbing these out will still allow the
callers to work unchanged, but in effect simply always return without
dispatching a promised task.
This fixes the dependency issue from part 2a.
|
|/
|
|
|
|
| |
- Exclude missed MediaKey functions and CDMProxy code.
- Exclude EME APIs frm being built (webidl change)
- Fix tests in --disable-eme state
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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 #1344
|
| |
| |
| |
| |
| |
| | |
when the attribute value is an empty string;
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
the constructor.
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
even if some of elements are already unlinked
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
MutationObserver to use them
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
non-custom element
Tag UXP Issue #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 #1344
|
| |
| |
| |
| |
| |
| | |
prototype swizzling for custom element
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
CustomElements feature
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
validation checks
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
removing parts of v0.
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
sending callback.
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| |
| |
| | |
"create an element for a token".
With fixup for missing header due to unified builds.
Tag UXP Issue #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 #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 #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 #1344
|
| |
| |
| |
| |
| |
| | |
ensure upgrade reactions aren't scheduled to BackupQueue;
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
CustomElementUpgradeReaction;
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #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 #1344
|
| |
| |
| |
| |
| |
| | |
(v1).
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
when possible.
Tag UXP Issue #1344
|
| |
| |
| |
| |
| |
| | |
CustomElementData.
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|
| |
| |
| |
| | |
Tag UXP Issue #1344
|